• Resolved darchik

    (@darchik)


    Hi all. Upgrade to 2.7 fromd 2.6, change all files, and then write to me

    Fatal error: Cannot use string offset as an array in public_html/blog/wp-includes/capabilities.php on line 116

    cant do nothing. when go to upgrade.php – same error. ??

Viewing 8 replies - 1 through 8 (of 8 total)
  • you have a widget or plugin issue.
    did you deactivate the plugins before upgrading?

    Thread Starter darchik

    (@darchik)

    plugins – yes. all!
    theme – no. and theme with admin interfase not work together – so admin must work. ??

    Thread Starter darchik

    (@darchik)

    All ok. ill resolve problem myself.

    its about config.php – must reload new config.php from 2.7 lol

    I am getting the same error.

    its about config.php - must reload new config.php from 2.7 lol

    Do you mean “wp-config.php” file? If so, what did you do to reload it?

    I have the same problem… I change old wp-config.php with newone… any help maybe?

    Thank you

    in .htaccess add:

    php_flag magic_quotes_runtime off
    php_flag quotes_gpc off

    I tried all this but nothing works .

    I have php5-5.2.8 , php5-mysql-5.2.8,apache-2.2.11 on my server.

    Now i have this error

    Fatal error: Cannot unset string offsets in /usr/local/www/blog/wordpress/wp-includes/widgets.php on line 621

    Any help appreciated…

    I changed this in my php.ini file, restarted apache and all was well.
    php_flag magic_quotes_runtime off
    php_flag quotes_gpc off

    However I am running this embedded in a Joomla 1.1.x site which prefers:
    php_flag magic_quotes_runtime on
    php_flag quotes_gpc on

    So I guess they do not play nice together.
    It is my belief that requiring this setting to be off is not good. Magic_quotes_runtime on is there for a reason with frameworks like Joomla that have over 4000 extensions by 3000 developers. Sometimes a little wiggle room is helpful.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Error in capabilities.php after upgrade from 2.6 to 2.7’ is closed to new replies.