SpikeTheLobster

Ditto for me: horrible, horrible update, though I hate to say it. Lost all my options, had to rebuild everything, front page is now fugly, layout’s gone to hell. Thank goodness for older versions.

This kind of update should have been separated into a “MB v2” or “New Magazine Basic” as a totally different theme, in my opinion: it’s changed significantly and requires a totally different approach.

Ditto for me: I’d love to be able to set up a cron job to run through all posts in a given publishing state (pending, draft, published, whatever). It’d save me a lot of hassle with multi-author setups where some of the individuals are, shall we say, less concerned than they should be with external image linking!

I found a way to do it using a shared user table and some other stuff. Works a treat and is much more flexible/manageable than Multisite.

“the majority of WP themes and plugins work just fine on Multisite” – your mileage is obviously better than mine: of the plugins I wanted to use, a good 30% didn’t work. Maybe I have a knack for choosing the odd ones that refuse to cooperate but it really was a complete nightmare.

Thanks for the pointers, though!

@mika – yeah, that was more a note to myself than anything. ??

My main problem now is that MU sucks for setting up most of the plugins I need (since they have either hardcoded directory paths or caches). Very annoying that there isn’t just a “unified login” for normal WP, really. So much extra work to get one or two features. Ah, well.

At least the domain mapping thing is sorted. Thanks. ??

@mika: Update – it worked a treat, thank you. Now if I could just get the www version of the sub-site to work as well, I’d be sorted.

@derrick: There are two different “park” options on GoDaddy (and with most hosts). The one that points to a bunch of ads is the “park this domain because I have no content” option done through their domain manager; the one I’m using is the WHM one on the VPS, which parks one domain on top of another. I guess the shared hosting equivalent is redirection or something.

For the wildcard domains thing, I thought that was for the subdomain version of the MU setup – I’m using the subdir setup.

As far as that “configuring the machine” thing is concerned, I’m afraid it’s all in Chinese for me. :o\

Incidentally, could I just point the second domain at the subdir and not bother with mapping? I’m the only person who’ll be managing that stuff so I don’t need something friendly for sub-net admins or anything.

I have a feeling that would confuse matters and be more error-prone (especially for me) but thought I should ask. ??

Aha… that’s the hole in my knowledge!

They’re on the same VPS so the IP’s the same, nameservers are set to the same address (even when there were two sites).

So I just log into WHM and park https://www.subsite.com onto the same account as https://www.mainsite.com? I’ve done that before (with .net and .org addresses to the same TLD) – easy peasy.

I’ll do that, wait a bit and see if it works. Thanks very much for filling in the gap… fingers crossed!

Same thing happening here: it doesn’t work except under VERY specific conditions – namely, that the image has to be added to the post by uploading it, not by adding from the library, etc.

It also only seems to run once: if you add an image to a post, then decide you don’t like it and remove it, then upload and add another the FIRST one still appears as the featured image.

In my opinion, these inflexibilities massively limit the usefulness of the addon. It would be much better if it checked and updated when a post is Published or Updated, rather than when an image is added.

Edit: went looking and found Auto Post Thumbnail by Aditya Mooley, which seems to do the job and has a button to process old posts… but doesn’t have the post/page switch. Suits my particular needs better.

Ah, well. I’ll find another plugin. ??

Ditto for me – bad, bad, bad decision to remove the button IMHO, especially without an option to put it back.

Any pointer on putting the button back would be VERY much appreciated as the plugin is completely useless without it. Contributors who are new WP users simply don’t know about changing post status manually (and it’s a lot of extra clicks, too – 5 instead of 1).

Doubly confusing because it’s still there on the Quick Press widget in the dashboard.

I’d like to but the site is live and the popup is a disclaimer that’s very important. I can’t just take it off as there could be legal ramifications. ??

Notes: using Magazine Basic theme with W3 Total Cache, Editorial Calendar, Akismet, AIO SEO, Jetpack, Contact Form 7, Google Analyticator, Solve Media and WP Missed Schedule. No conflicts.

Actually, forget it. I just discovered that there are no comments per picture available in NextGen, which makes it totally redundant for my purposes. ??

Presumably, this is because of Google shutting down the old API that made authentication possible (Google Analyticator is also dead because of it). Guess we have to wait until someone updates their plugin to work with the new setup, then all rush to get that one.

Until then, enter the code manually and just let it track. ??

“Oh, you don’t like hooks. Well that’s the only way to properly extend WP functionality.”

I don’t want to properly extend it. I want to add a simple check, rather than invest hours of time in learning a pile of stuff I’m unlikely to ever use again.

“You can put the code in a new plugin. I’m afraid you’ll have to get your hand dirty on some code, but it isn’t that hard to be honest.”

It is when you have to start from scratch and learn all the “how to code for WP” stuff – the time investment is absolutely massive for one simple check, which is precisely what I want to avoid.

Ah, well. I guess I’ll just live with it for the moment – at least until I have hours of spare time to put into all the learning (and reading that awful codex).

Thanks for the input, guys.