Jump to content
SAU Community

Recommended Posts

Ok this is weird. I've just upgraded from FF 3.5.7 to 3.6 and now when I go to make a new post on this forum, the main text box is uneditable. You can select any text that might be in there, but can't delete or change it, nor type new text.

To get this text here I've clicked "Insert special item" -> Centered text, and filled in the field.

I can still edit the post normally, but only using quick edit, so the centred text should be edited back to normal by the time you read this.

Haven't tried replying yet, but I suspect the same will apply, will only be able to use quick reply.

Edited by Lum
  • Replies 58
  • Created
  • Last Reply

Top Posters In This Topic

  • 1 month later...

Its actually a bug with IPS 2.3.6 - All users of Firefox 3.6 are going to experience this issue (as you can see, I cannot type text underneath what has been quoted as the cursor is not letting me place it where I want. There is a patch here.

http://community.invisionpower.com/topic/3...or-ipboard-236/

Could we please get that patch loaded into the server? Others will have this issue as they upgrade from 3.5 to 3.6.....

Many thanks

-Dohmar

Well it's nothing we can help you with mate.

You should report the issue via Firefox's reporting/issues log.

I'm using 3.6 daily... and have done so for a while... I still do not have this issue funnily enough.

Either way - we are migrating servers early next week.

I can't see any patching/changes in the next fortnight unfortunately - cant upgrade in the middle of a migration :(

its a strange issue. i downgraded to 3.5 and it works fine. Any chance of upgrading to ipboard 3 once the migration is complete (or convert the data and install 3 as part of that migration) - its very frustrating - are you using the basic editor

As far as the link is concerned, all that needs to be done is to replace a js file within the heirachy - its basically a re-coded subroutine for the editor to work correctly with 3.6's js implementation - should just be able to drop it in and have it work

-D

I'm using 3.6 daily... and have done so for a while... I still do not have this issue funnily enough.

Either way - we are migrating servers early next week.

I can't see any patching/changes in the next fortnight unfortunately - cant upgrade in the middle of a migration :nyaanyaa:

FF 3.6 and patch hasn't fixed quick replies or full replies from what I've experienced.

Quick edit works fine though.

Issue has to do with Firefox's change in JS engine. Will get onto it if no patch is issued by IPB in the next week or so.

I'm using 3.6 and I also suffer from all of these issues. Have to use IE to browse the site as it is just completely non functional in 3.6

Hope the patches are run soon otherwise the list of people experiencing these issues is going to grow and grow. Took me over a week to bother to even look for this thread, so I imagine that there are quite a few other users experiencing this that just haven't posted here yet.

Edited by Rolls

All the guys experiencing issues with FF 3.6, can you guys turn off all your addons and try using the forum? Just wanna make sure its not an incompatibility with one of the addons as I seem to be having the same issues when I have my addons enabled, but not when I turn em off. I haven't narrowed down which one though.

hmm. i've just updated FF to 3.6. still getting all the usual stuff with server timing out and stuff, but it seems to take forever to submit a post now. you can do it, but the tab just loads forever. the post can be seen as being submitted if you "view new posts" in a new tab though

I have FF 3.6 and have the same issues.

Have disabled all addons to no avail. And am having issues on two different computers on two different connections.

i have FF 3.6 and cant post a damn thing on SAU. (using IE7 :) for this) other forums i visit in FF work fine.

edit: works fine now. FF updated to 3.62 and all it good. :(

Edited by Peter89

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Similar Content

  • Latest Posts

    • Sounds like the rack seals blew.
    • ^ This is all good advice. I can imagine that there's some passive components in the HVAC controller that run that PWM output that could die, or suffer bad solder joints. It can be worth opening it up, taking a schmooze around looking for swollen electro caps, evidence of liquid escape anywhere, tracks that have been hot, lifted, cracked, etc. A DMM might not be suitable for seeing if the PWM output is pulsing. Might be too fast and too low voltage for a DMM to keep up. An analogue voltmeter might give a better hope. I use a handheld oscilloscope (<$100 from Aliexpress if you want something cheap). A DMM might see the voltage across the motor flicker. Otherwise, as above. If you can successfully see PWM action, then the control side should be good. If you can't see it with what you have, you might need to step up the instrumentation used, as above. Beyond that, and dbm7's advice on testing the motor directly, you're down to looking for broken wires, corroded connector pins, etc.
    • So Thanks for the comments etc. To follow up on this, we went down the path of fitting a divider down the middle of the external pipe that was added to the exhaust manifold and the divider went from very close to the external wastegate all the way up to the "V" part where the pipes from each side of the manifold joined. After this modification it was finally in a position to do the dyno-tune with some degree of success. Top end power was down about 10kw (250rwkw down to 240rwkw) I believe from previous but it seems to be more responsive lower down and at least it is now driveable and fun and back on the road to be enjoyed. Apparently the timing couldn't be run the same as it was running into knock and boost was down about 1psi. For all we know this could have been from the fuel being a bit older, or perhaps some slight complication from the new head gasket as we didn't have compression figures from before that mod to compare. I'm no mechanic and this is second hand info but I just wanted to follow-up to those that commented or read the original post with interest. After so many months of stuffing around this is a big win. The interesting part was most of the info around this was gained from information around Barra motors and not GTR as the manifold setup on the Barra with single turbo was more similar.  Thanks for those that helped with info. Regards Rob 
    • G'day ... first up, I very much doubt that's a resistor network (as used also for this job), but the part# looks right. The description of 'power module assembly' looks to be nissanese for 'PWM driven, ground switched, DC motor speed controller'.... the circuit in the schematic kinda infers that's the case... ...with the transistor symbol appearing in the unit described here as 'Fan Control Amp(lifier)'....being driven by pin20 on the HVAC unit,  and a feedback signal on pin19 from the motor negative terminal for some reason (might be motor fault detection, maybe they detect commutator switching to determine motor revs as well, I dunno)... but if they are  counting commutator spikes, a bad segment (or really worn brushes) will throw a spanner in the works... The motor itself will as said be brushed DC with segmented commutator, rated at 12VDC nominally ~ now-a-days I just unplug them, determine the positive wire, and hook them up to a variable power supply and find out how much current they draw, if they work etc etc ...you can also check for bad segments...ie; set the power supply up to feed 1volt @ 2amp max, then watch the wattage count as you slowly rotate the fan blower motor through a complete revolution ; any bad/dead segments will be clearly evident...some folks would just say determine the positive wire, and feed it battery voltage, and if fan spin, you've got a win...<grin>... well, at least that infers it should do something when plugged back in, and the HVAC unit commands it to run... and if it doesn't, you suspect the module, but you should check the PWM signal on pin20 is actually present, and if it is, blame the module ...  
    • Ah. OK. I take it back. I hadn't looked closely at the R33/4 arms and presumed that GKTech did as GKTech do everywhere else, which is to use sphericals there. The poly bushings are made to be 100% interchangeable, should use the standard bolt just fine. Every other bush in every other place in pretty much every other car, does.
×
×
  • Create New...