mulgar

Yes this sucks, months on still can’t find anyway to prevent this other than manual upgrades and manually checking.

@andrew yes true, for this I probably manually updated but didn’t realise WP had selected an incorrect update for the theme.

It doesn’t really resolve the issue of why the update was allowed by a different vendor with same theme name to overwrite my present theme.

Obviously in future I’ll be double-checking this, but it opens up a concern on why this even happened (or is possible to happen again in the future) in the first place.

I had this same problem, after updating my theme all my formatting got wiped out, and it seems my StudioPress Prose theme was replaced by another theme with the same name.

This creates concern for auto updates if updates can not be trusted, and potential security issue if something like this could be targeted directly.

Yeah, I think I’ve learnt a lesson to regularly check the error_log now for any misbahaviour ??

Oh ok, thanks for the feedback. I think I’ve fixed the problem in the mean time.

I actually don’t leverage that plugin for too many pages, or users, so I just recorded the configuration manually, deleted the plugin, reinstalled, and then reconfigured the respective pages and users.

From what you are saying, I’m guessing maybe the termmeta table got lost in the upgrade to 3.5 somehow (not sure) and maybe that’s where the problem came about, or maybe it never truly installed properly in the first place and I just never noticed any issues.

This was only brought to my attention because my provider pinged me on disk usage with the error_log growing large.

I checked and there is now a termmeta table created, so I assume the errors will stop. It looks like the errors in error_log have already stopped.

From what you are saying (and since I don’t rely on this plugin too much anyway) I might look for other options or see if I can remove the plugin altogether if I don’t need it and it isn’t compatible.

The only thing I need to do to close the loop on this is check if I can restrict the growth of error_log (which grew to an unreasonable 1.7GB).

I really appreciate your response here so I could get to the bottom of this, thank you very much for your help!!!

Thank you so much for your response and lead Josh!

Yes you are on to something. I do have Contexture Page Security plugin enabled, so this is most likely part of the problem. It’s kind of weird that I haven’t noticed any functionality issues yet.

Let me look further into this plugin and see if I can pinpoint this, maybe I can reinstall it or something to get the table back.

Bugger, I didn’t really think of that or test that piece out, but now that I look into it I find that notifications aren’t working for me either. I checked the email address configured, and the FB ID configured is correctly but if a comment is made get no notification either by email, facebook or wordpress that a new comment has been made.

This is not good and could be a show-stopper for me, I’m running a church website so I need to be notified to manually moderate comments if anything inappropriate is being left. I might have to look into the approve each comment setting, but even then if I’m not getting notified of new comments then this is going to be painful.

Let me know if you find anything out on this, may need to disable this plugin until these issues are sorted out ??

Do you mean under Advanced Settings? I also see the “Comments xid” box as empty. This could be expected behaviour the help mentions xid is randomly generated but I guess it would be nice if it was displayed to user as well.

I did get an email when I activated the plugin but it just said: “We just thought you’d like to know that your current XID is: .” so that didn’t help much either.

I must say everything is working okay for me without knowing that xid (except for this). But I would be kind of stuffed if I ever needed that random ID to reset things.

Yeah I had that same issue and wasted some time on that.

I highly recommend to plugin publisher to enable those checkboxes which are required for it to work as default settings or at least add that as clear information in the FAQ it could save some new users of the plugin some headaches.

Thanks for your reply ahamade86, I’m glad to hear it’s not just me facing this problem. Since it does seem more like an issue with the plugin hopefully it can be resolved in a future update.

In regards to the other issue about both links on the facebook wall post going to the article itself, I think this seems to be working fine for me. On facebook I have a post which is something like “(me) commented on (article name with link to article) on (website name with link to homepage)”. For a Like (as opposed to a comment) it seems to be the same deal (working okay). Sorry not sure why it’s working for me but not you.

FYI forgot to mention before I’m using “v2 only” parameter in the plugin configuration, not sure if this is relevant to the issues.

Is anyone else facing this problem? Can anyone provide any guidance on what we should be looking to here? Cheers.