Hi, since updating to WP 3.1 and also updating Sitewide tags and other plugins, my main page blog (which I was using as a portal via Sitewide tags) is empty, reading 0 posts on the dashboard and saying the archive is empty on the page. There were posts in this blog too, so they are gone as well as the ones which were displayed from the subdomains. (Although maybe they have been pushed over the sitewide tag number limit by the posts from the other blogs.)
To make this even more difficult to manage my plugins page is empty, so I can’t activate/deactivate the plugins to see what is causing it.
Also I can’t find the sitewide tag admin page: I’m very lost on the new dashboard.
I am getting a message saying.
Also the dropdown buttons for settings, themes etc are not working so maybe its some sort of general problem causing these things.
Its hard to know where to start because I’m not sure if one problem is primary causing the others or there are several seperate problems and my dashboard functionality is limited re: plugins etc.
I’ve heard there is a sitewide tags issue in 3.1 so hoping that is on its way to being fixed but worried it is some sort of database issue.
I should add when I remove the plugin via cPanel (because I have no plugin control) and re-install it I get this error:
Plugin could not be activated because it triggered a fatal error.
Fatal error: Cannot redeclare sitewide_tags_update_options() (previously declared in /home/dallasm/public_html/wp-content/mu-plugins/sitewide-tags.php:106) in /home/dallasm/public_html/wp-content/plugins/wordpress-mu-sitewide-tags/sitewide-tags.php on line 299
OK, so re-reading that error message I realised sitewide tags used to be in the mu folder, so I’ve removed that one, (still no posts) uninstalled the new version, reinstalled it, and now I have the admin menu for SW tags.
When I try to save the settings or populate the blog, the screen goes white and nothing happens: when I reload the pages, the changes haven’t been saved (so it seems like this isn’t working)
I also did a test post to the main blog and it isn’t taking any posts (says 0 posts and doesn’t show up)
So it seems like sitewide tags wasn’t working bc in wrong folder but also I just can’t post (plus there are no plugins showing)
I’ve tried dropping the number of posts to 10 and removing options like images. Once it didn’t time out but instead went back to page but with the plugin disabled again.
Tags Blog Enabled (box empty)
Sometimes I get this error when I try to populate posts
This webpage has a redirect loop
The webpage at http://incairns.net.au/wp-admin/network/settings.php?page=sitewidetags&action=populateblogs&_wpnonce=c61e0c18c4&_wp_http_referer=%2Fwp-admin%2Fnetwork%2Fsettings.php%3Fpage%3Dsitewidetags%26action%3Dpopulateblogs%26_wpnonce%3Dc61e0c18c4%26_wp_http_referer%3D%252Fwp-admin%252Fnetwork%252Fsettings.php%253Fpage%253Dsitewidetags%2526action%253Dpopulateblogs%2526_wpnonce%253Dc61e0c18c4%2526_wp_http_referer%253D%25252Fwp-admin%25252Fnetwork%25252Fsettings.php%25253Fpage%25253Dsitewidetags%252526updated%25253D1%2526populate_blog%2526populate_all_blogs%253D1%2526c%253D10%2526p%253D200%2526updated%253D1%26populate_blog%26populate_all_blogs%3D1%26c%3D10%26p%3D200%26updated%3D1&populate_blog&updated=1 has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.
Here are some suggestions:
Reload this web page later.
Learn more about this problem.
I did everything I could think of to get this working, in the end deactivated all the plugins, played round with plugin settings etc restored old database with no success.
Changed from 2010 Weaver to default 2010 and finally it worked,
then continued to work fine after reverting to custom child theme based on 2010.
So success after many hours of frustration!
Backup DB and files, turn off plugins etc,
A good experience in the end, thankfully.
Learnt a lot on the way!
- The topic ‘Main blog empty: Site Wide Tags or DB issue?’ is closed to new replies.