Derek Jones - 09 February 2010 02:36 PM

...the file should get you by until you are able to do so.

Derek do I just drop core.extensions.php into system/extensions, and then delete $conf[‘allow_extensions’] = “n”; from config.php?

Thanks.

It would go into /system/core/.  Backup and replace the core.extensions.php file that you find there.

Just wanted to jump and and say thank you for this thread. I was upgrading 2 sites on the same server. One upgraded no problem. The second would throw me this error when logging into the CP. For some reason one site was on PHP5 and the problematic one was on PHP4.

My mind was truly being boggled as to why one would work and not the other. Made the switch from PHP4 to PHP5 on the problem site and all is well. Thanks for your work and dedication.

The good folks at EngineHosting expeditiously upgraded me to PHP Version 5.1.6 and now all is working fine : )

Just wanted to second setheryb and say thank you Derek for your diligence on this thread. Had exactly the same problem with a different set of extensions. Rolling back core/extensions.php has fixed the issue.

Also have the same error on extension,

I would like to roll back but unfortunatly did not backup correctly!
Is there anywhere to download V1.6.6 ?

No, you cannot download older versions.  Are you on a host that can switch you to PHP5?  On most hosts, this an instant switch that would fix the issue for you.  If not, let me know and I will email you an appropriate file.

Hi Derek,

Unfortunately i cannot switch to PHP 5, is there a way to manually remove the extensions? i have set extensions to disabled and tried removing them from the system folder and re-enabling them but they are still looking for them?

You could do so manually from the database, David, in the exp_extensions table, but then you’ll lose the functionality of the extensions you’re using.  Hang tight for a new file, I’ll send it your way momentarily.

Thanks a million Derek for the quick response!!

SUPER support

Hi there.

Any thought to releasing a build that doesn’t cause this site-blocking issue? I got bitten by it again tonight during an otherwise routine upgrade.

TTFN
Travis

Yes, it’s scheduled, Travis, sorry for the inconvenience.

Thanks for this thread everyone.  But after reading through and checking my configuration, I’m not sure why I’m having the following error after attempting to enable lg-tinymce.1.3.3:

Warning: Missing argument 1 for show_full_control_panel_end() in /homepages/31/d196439351/htdocs/.../ext.lg_tinymce.php on line 989.

I’m running 1.6.8, build 20100121 on PHP 5.  I’m new at this, so I’m sure I’m missing something.  Any thoughts?

What version of PHP5, Nathan?

Hi Derek,

Thanks for the quick response.  Turns out it was MySQL 5 running on PHP 4.  I added

in .htaccess (per the host’s instructions) and it works fine now.  Does this seem like a good solution?  Thanks again.

Yes Nathan, that’s just fine.  The next build will again give you the choice of running in PHP4, though I’d advise staying on PHP5.

And just to close things out- this should have cleared up in the 415 build/