FF Web Dev update.

update:

Apparently, according to the web dev forum this is expected behaviour and the fault of the browser :? (never happened before!) standing advice has always been to re-install Firefox :? well that didn't solve anything!

I'm rolling back to the previous version if as Chris Pederick says it's still available ?

I've rolled back to 1.0.02 which is still posted on the FF extensions page.

I also took things for granted and auto-installed the update but all is working fine for me.

I like where the style information comes up just below the toolbar and when I use edit CSS I can alter the size of the viewport for that function as well as easily setting it to the left, above or right of may main viewport.

P.S. I had never used the edit CSS function before, and it's amazing so thanks for this post Hugo as I would not have known I could do real-time editing, this will save me buckets loads of time making a change then ftp'ing my new css shett up and then refreshing my page

Well it's an odd one then as Chris Pederick seems not surprised by someone mentioning that the DOM inspector breaks even sounding a little terse in his reply on the subject, but I have never had a problem before and the DOM inspector still actually works despite 'View style information' reporting it wasn't installed, so methinks it is a problem with web dev rather than FF.
I'm not bovered though couldn't see any major advances in 1.1 so will stick with 1.0.2 until 1.1.1 is released.

'Edit CSS'is a useful function but positioned at the bottom of the screen :? don't see the point just means you can't see many rules at one time, if that is, you want to be able to still see the actual page and results of changes.

Actually I edited it to reflect the 1.1 update but the link is the same. The localised versions are also the 1.0.0.2 release.

Actually I edited it to reflect the 1.1 update but the link is the same. The localised versions are also the 1.0.0.2 release.

You've lost me TPH, clarification please. Me brain is mush today.

Oh I thought by FF Extensions page you were referring to the list here

Ah I see sorry I was referring to the FF page which still has the 1.0.2 version posted although 1.1 is being offered via auto updates, anyways I'm done with it, 1.0.2 works nicely I have a feeling 1.1 might be a little buggy there certainly seems quite a list of bugs to fix up.

I've just noticed a 1.1.1 update is available, that may solve your issues

ah that was a speedy little update then

did it solve them?

I've held off on updating while you do your guinea pig impressions

I'm with Chris, Hugo. Is it ok to update, yet?

cheers,

gary

Hello human chipmunk here, er guinea fowl

No dam thing is still broken, can't help but think it's a problem my end but have now installed 1.1, re-installed FF over top of existing copy as recommended, got cross, re-installed web dev 1.0.2 over top of 1.1 - back to working.
Installed 1.1.1 over top of 1.0.2 no joy, un-installed all web dev clean install of 1.1.1 no joy, re-installed 1.0.2 couldn't be bothered to try re-installing FF. I rely on 'view styles' too much to not have it working and until such time as I see verified reason for problem I'll stick with 1.0.2 which is fine.

I would say that with all the faffing around installing/un-installing I seemed to suffer no ill effects so it may be worth someone else having a go and confirming that I'm the only one having this problem

I do not have any problem with the new update. The SeaMonkey version checks css (console).
The edit css and edit html can be located anywhere and are much better than the version 1.0.2.

Hugo what problems are you having with it?

The new update gave it a facelift but you can set it up how you want.

Want the "edit CSS" window as a sidebar instead of at the bottom? Just click the "position" icon next to the "edit css" tab in the window.

Hmm - my version is still 1.02 and Firefox hasn't offered me the upgrade option and when I click on the "upgrades" icon in tools/Add-ons it doesn't find anything. Odd.

Ed it could be that you have not got Options > Advanced > automatically check for... enabled ?

Folks I was kidding about the viewpain for CSS edit and did figure out quite quickly that it could be undocked and moved, it just struck me as a particularly daft default placement of it, if one thinks about the general prefered format for css text files of around 30 odd characters wide stacked up vertically.

TPH the problem is that the blooming update breaks the functionality of 'View Style Information' reporting that I have not got the DOM inspector installed despite the fact that I have and always have had and use it often. Trouble is that 'View Style..' is a feature I use more than anyother probably, a quick scan of the web dev forum only threw up one post regarding this and it was somewhat brushed off as being a browser problem :? which I find hard to believe as logically that is not the assumption that would be arrived at.

Well, I DON'T have the DOM inspector installed and webdev view style info works fine for me?

Try removing the domi and see what happens?

Try removing the domi and see what happens?

Do what ?! you must have the DOM inspector installed it's integral to many features and part of the initial install of Firefox, you can easily not install it though as you need to select 'custom' when installing Firefox.

I think the update looks to the site where it got the extension. So, one source may be ahead of the other.

cheers,

gary

How do you mean Gary? have I missed something?

The view style works for me and the DOM inspector can be reached through the Tools drop down menu.
Did you try to install the extension on a new profile ?

yep always have been able to access DOM through tools, still can!

New Profile? what in error?

It could be, but as a matter of fact it isn't. I do have this option enabled both at home and at work, and in FF prompts me to install various extension updates all the time. I haven't had a new update after WD 1.0.2 on either system.

Also I just went to the WD site and they don't mention anything beyond 1.0.2 that I can see - Oh wait!, they do mention 1.1.1 but it wouldn't install to Firefox 2.0.0.1 - the install package says it is imcompatible.

Hmm--well 1.1.1 seems to have installed in Flock, but the WD toolbar disappeared after a restart.

Well there is something wrong somewhere.

Yeah, there definitely is. I removed 1.1.1 from Flock and reinstalled 1.0.2 and now I have my toolbar back.

I did miss a post on the web dev forum linking to a number of previous threads on the subject and there is a note on 'downloads' all suggesting that the DOM breaks and re-installing FF in custom mode, ensuring all old files removed before hand, and/or creating a new profile sorts things out.

As I dont concider any of these as identifying the root cause and I dont need another profile I'll leave things alone for the moment.

I guess you're all at FF2.0.1 then

Except for me, who's been using 3.0a1 occasionally

Thought: ought to try the extension on the 1.5 install and see if the same problem occurs.

TPH do you always have to be so avant guard?

Yep Just building up my new PC and have just installed Adobe Reader 8 (much slicker logo and interface) and Flash Player 9

Just a quick update to let you know 1.1.2 is out

Version 1.1.2
January 19, 2007

* Fixed bugs:
o 'Display Line Guides' and 'Display Ruler' did not enable and disable correctly when switching tabs
o 'Edit CSS' lost all styles when the page was refreshed
o 'Remove Maximum Lengths' did not work
o Color information was not output correctly
* Various minor code fixes

The version updates roll thick and fast.

Still says nufink about my problem :mad: so I'm not going to bother, I'm going to wait for 2.5.9

Ought to just update this thread.

Finally got fed up with Firebug not working correctly so followed the advice to perform a full uninstall of FF and clean install.

It is an FF problem upgrading (over) from 1.5 to 2.0 whereby some old files hangaround? and disrupt the DOM inspector.

Firebug now works fully.

Haven't yet updated WebDev toolbar but expect no problems.

Pssst . . . it's now up to 1.1.3

Bloody versions, bane of my flipping life, seem to spend all my time upgrading things, hopping mad at WP once more as it seems back on it's incessant version upgrade madness, got round to installing 2.0 left things for a scant two/three weeks before having time to look at changes/improvements to it , only to see that not only were there some ~4-5 minor revision upgrades but it had moved on to 2.1 :mad:

It sounds like WP is going to be doing a lot more in the coming year too.

Oh great! then they need to think about how they roll them out and if fixes then be sure to list exactly the files that have changed cos I'm not deleating and uploading all of them everytime, someone used to post a list of changes found and in which files, dont know if he still does.

all these minor versions fixes worry me, too many in rapid succession

What I do (sometimes) is use version control s/w to make a patch between my version and the standard version. Then I can either use same s/w to make a patch for the version upgrade to apply to my version or apply my patch to the new version. Its not always 100% but it can save a lot of time and it does track all the changes I have made.

That sounds rather sensible, and food for thought, have to admit that they do produce a changelog of sorts but not always where one thinks to look for it.

I still tend to think that WP is just not that well thought through from the point of view of architecture, simply too many files, drupal seems so much leaner and better thought through, and doesn't seem to find security problems two seconds after releasing the last patch/version

Unless the changelog is automatically generated you can never be certain it does in fact contain details of all changes.

I'm not a fan of Drupal, so don't get me started

You're not a fan! I'm in despair of ever finding a true CMS that doesn't have some majorish drawback, spent so much time with Drupal that I should be close to being a Guru but still feel I can't quite get the API sorted in my head and laugh when I find that to do something fairly straight forward would require writing a 'Module'

I feel the same.

CMSMS is a little more straight forward but to my mind still overly complex. For all of these systems (that I have come across) the documentation is woefully lacking. For me the huge advantage of using tools like PHP, MySQL, Smarty is the comprehensive and accessible nature of their documentation.

(Before anyone jumps in to eulogise about their favourite - some of these are no doubt superb applications. However the learning curve involved in customising anything beyond the most basic is time consuming, frustrating and hampered by a lack of documentation).

I've tried most so probably like you am not interested if people start to eulogise about their favs, it's not the point, the documentation is fractured at best, it may be there but to find and piece together is often too time consuming, many of them don't really know what they are (Drupal springs to mind) is it a blog is it a CMS or is it that elusive thing a community portal :? WP likes to claim it's capable of running within/as a part of a static site so now more a CMS but I don't see it personally. Too often one is twisting what has been written to perform one purpose to suit another or worse stripping down and removing functionality.

All that is required is a commonsensical template tag system allowing content as objects that can be defined to regions and that can be easily edited by newbies sadly I need along with that a basic blogging system and the functionality that the admin interfaces bring, I could doubtless get the template tag part together (if I thought I would use it enough to warrant the time) but the blogging and editing interfaces would likely defeat me especially from the point of view of ease of use for a newb,so once again I find myself stuck with Drupal pondering how to the simplest thing yet while often achieving quite clever complex things that I just don't need all the time still feeling as though I'm struggling to learn the dam thing, and as ever just getting a little bit frustrated by documentation that is compiled by too many disparate entities with differing commands of the English language and views as to what constitutes clarity (do not use the word 'module' loosely it has a flipping specific reference with drupal and gets someone looking to the wrong files.)

One product I haven't returned to is Textpattern, which from my initial flirtation looked interesting, but iirc I think it crashed on me, without any possibility of resurrection,which always sort of puts me off if I'm to offer it as a choice to power someones site.

If anyone has any interesting comments on Textpattern from experience, it would be interesting to hear them.