Looking at it some more it appears that the shortcodes have changed
from [pc-pvt-content allow=”53″]
to [private role=”administrator”]
Any way for me to correct this without needing to edit every page on this site?
Never mind. It appears that the developer that built this site used a plugin from code canyon that has the same name as this plugin and the WP updater appear to be getting confused
[…] a plugin from code canyon that has the same name as this plugin
Yes, and this is a serious problem. A lot of users have been confused.
May I ask you to tell me the date of the first release of the plugin on Code Canyon, if you know this info? Just a curiosity.
Here’s the link to it http://codecanyon.net/item/privatecontent-multilevel-content-plugin/1467885?ref=LCweb. According to the changelog it was first released Jan of 2012.
Since I do not have access to it I’ve bumped the version number way up in the file so I don’t have problems with it in the future. It appears to be working…. for now. I’m not really happy about the solution. Eventually I’m going to have to replace it but that’s going to mean editing almost every page on the site.
Could you tell me the old shortcode and the new shortcode?
The shortcode for that plugin looks like [pc-pvt-content allow=”53″]
The ID value is an from user types you create using the plugin.
And you have in mind to replace that plugin with mine? If so, you should change all the shortcodes. A plugin like this could help you in part (made a backup of your database before trying it). Or even a simple search & replace with a text editor.
Eventually, yes, probably. I’m assuming I’d need to use a plugin like user role manager to create the different user types represented by the ID values o in the other plugin and assign each of the current users to the right roles.
Today my main goal was to get WP core updated. It was several versions behind and updating is all they client is getting right now. Like I said, the current plugin is working and I looked it over and did not see anything that concerned me security wise. The time for doing more needs to be presented to the client. Honestly I’m more worried about updating at all with the information I have. There’s nothing to say that the new version from there will be backward compatible and I’d still be in the same situation.
This is irritating for me because the original developer obviously purchased a plugin but did not bother giving the client access to the account, though I don’t know if updates are included. It’s not all that expensive but I’m not a fan of code canyon and I’d prefer to just find a way to replace it with something I can trust.
By the way, I just took a look at your stats page. I’m surprised that you haven’t gotten more of these. If this was my plugin I’d be contacting the powers that be to see what I needed to do to fix the situation.
I’m not really interested in stats. I released all my plugins only to give my “thank you” back to the WordPress community. 🙂
I just mean, all the version numbers represented in the stats that are for this other plugin that gave me the issues.
I already contacted one of the admins and there is no solution.
