asternick
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Invalid argument supplied for foreach() capabilities.php on line 31From the link:
So, in summary: if you’re locked out of your blog and get a warning/error about wp-capabilities and some invalid foreach() loop thingy, head for PhpMyAdmin, and look carefully through the wp_user_roles field in the wp_options table. If it’s split over two or more lines, or contains funky characters, you have probably found the source of your problem.
I have not been able to find any bad characters, nor is the field split. However I’ll keep poring over it in the hopes of finding something that does not fit.
Argh!
Forum: Fixing WordPress
In reply to: Invalid argument supplied for foreach() capabilities.php on line 31For a bit more detail, I am in a shared hosting environment and my sysadmin tells me .htaccess will not work so I used php.ini in the root of my blog directory for the php_flag fixes. I installed with fantastico deluxe. Any help much appreciated.
Thanks,
AndrewForum: Fixing WordPress
In reply to: Invalid argument supplied for foreach() capabilities.php on line 31Thanks for the script, dmry, but I am still having the problem:
Warning: Invalid argument supplied for foreach() in /home/menopaus/public_html/blog/wp-includes/capabilities.php on line 31Warning: Cannot modify header information – headers already sent by (output started at /home/menopaus/public_html/blog/wp-includes/capabilities.php:31) in /home/menopaus/public_html/blog/wp-login.php on line 12
Warning: Cannot modify header information – headers already sent by (output started at /home/menopaus/public_html/blog/wp-includes/capabilities.php:31) in /home/menopaus/public_html/blog/wp-login.php on line 24
Warning: Cannot modify header information – headers already sent by (output started at /home/menopaus/public_html/blog/wp-includes/capabilities.php:31) in /home/menopaus/public_html/blog/wp-includes/pluggable.php on line 391I also tried the php.ini fix to no avail (php_flag magic_quotes_runtime off). This is a fresh install of WP 2.3.1 which is producing these errors, and I could reinstall with no problem, but of course the problem comes right back.
Anyone else see this on a fresh install of WP 2.3.1 and find a fix? As you might be able to tell since this is my first post I am a WP n00b!
Thanks,
Andrew