andysocial

I’m dim. I somehow ended up with an enable multisite definition even in the “backup” wp-config file. I’ll go hide in shame now. Thanks for your patience.

After uninstall, reinstall, reactivate and still seeing the same error message, I just switched to a different XML sitemap generator that is happy with Multisite installs. It’s curious that the Arne Brachhold XML plugin still thinks I’m in multisite without those tables or config files. Must be something subtle…

Thanks. I figured site and site_meta, blogs, and blog_versions, but I wasn’t sure about the others.

OK, I’ve dropped those tables, reset the .htaccess and wp-config.php files to their old values, and still Google XML Sitemap says it just KNOWS I’m running multisite and hates me for it. Should I just give up now?

Google’s XML sitemap says it doesn’t work with multisite. Everything else is happy. But, since I don’t actually have any intention of running a multisite network, I’d just as soon revert.

Why did I enable it in the first place? Cuz it looked interesting and it’s good to know more rather than less. ??

Sure… um… What are the extra tables? I don’t tend to troll through the SQL frequently, so I’m not 100% sure which ones are the newbies.

Still getting this behavior, and no amount of changing things makes a difference. Apparently I need to learn Javascript to keep the functions that I had with 1.5.2 working in 2.0…

So, I guess the consensus is “several people have this behavior, and nobody cares.” Got it.

I hate that I have to report this, but it seems to not remember me in Firefox, but remembers me just fine in IE. Oh, the horror.

I tried clearing all cookies and other history, and yet – still forgets me every time. When I look at my cookies in Firefox, there are a couple from my WordPress installation, named WordPressUser and WordPressPass.

I’ve even tried using different themes (my norm is Neuron), and the same result. In IE, my blog remembers me; in Firefox it doesn’t. Other sites remember me just fine (although I now have to re-set them all after nuking my cookies).

Fantastic. I don’t have to hack the path statements for the CSS any more, and the additional features are great. How do you find the time for this?

Just deployed your new code, and it works like a champ. You rock.
Thanks for all the effort on this – it’s a great tool.

One thing I’ve encountered in my error logs, which I have fixed by hacking the PHP code – directory paths. They’re set to ../wp-content etc. This seems to cause no end of errors on my system, creating “file not found” errors for all the CSS files. So I fixed the code on my system by changing to /wordpress/wp-content etc. instead. This is something that might be coded into one location?
Regardless, it still doesn’t work at all on my system. It runs, but nothing like a decent result happens. The LJ-Synch module doesn’t send a post to LJ. The LJ-moods module doesn’t pull the graphics from LJ. I haven’t tried the LJ tags support yet, but the only thing I was actually hoping for was lj-synch.

Tcervo – you found it. Thank you, thank you, thank you. It was driving me buggy.
This is, of course, why I usually don’t use CSS I don’t design myself. This is one convoluted stylesheet.
Thanks again.

Maybe I’m dense, but why not just make static HTML pages and add the code to the index.php file as straight HTML? Why go through such complicated machinations to have content in the SQL database which is not “really” part of the blog (i.e., no comments, etc.)?

https://www.www.ads-software.com/support/3/6411#post-10
The referenced link shows a fix, although one that will be overwritten every time you update the core WP files. Not optimal, but it makes the calendar not broken.

The limitations of the post-by-email feature seem to be twofold:
The post only becomes visible once the server time meets or exceeds the email sending time. This is an issue if (like MANY people) your host is not in your time zone. If you are in New York, and send an email post to your server in Seattle, the post won’t show up for three hours. This does not seem to be intentional behavior, based on the various support postings I’ve followed on this.
Second, the Permalink URL for your post won’t work at all if you use the SLUG feature of the URLs. The email-post feature does not set the SLUG and so your permalink will be broken until you log into your server and fix it manually. This also does not appear to be intentional behavior, but no fix for it have I found.