thvs

Update: I found a hack to get around this issue.

It seems in my scenario/situation the theme I was working had made use for additional user roles in the theme’s functions.php file. this caused a conflict with the plug-in being used so it was not a plug-in specific issues as much as it was theme’s functions.php issue.

The simple solution was adding the wp remove_role function before using the wp add_role function in the theme’s functions.php file. From here the error message went away and the plug-in worked as it should. Point of interest, look into the intricacies when using add_role and remove_role wp functions and how one should go in front of the other, also (perhaps of interest) these functions may want to be revised/weeded out before deploying to the live site.

https://developer.www.ads-software.com/reference/functions/add_role/
https://developer.www.ads-software.com/reference/functions/remove_role/

@tara got it thank you,

see it got it,

@james Huff thank you sir, I will look into that.

mrtom414, I think you are right, I’ll try it out, thank you sir for your help, you are a gentleman and a scholar! ??

Thanks mrtom414, sadly I only have a regular theme with fixed width css layout for the content and client does does not want a redesign/update for regular (so much for mobile first approach), that is why i am inquiring about a child theme, because a lot of styles remain the same just the containers need to be adjusted to 100% width for mobile user-agents.

Update:

So I was debugging the code on my local machine, using the last backup (which was about 3 years old), so it seems DB and WP are linking YET it keeps shooting out more errors (see the link: https://i.imgur.com/VRJCNk1.png) when I fix one (usually by commenting out code in functions.php) another error rises. I may, unfortunately, find myself without an old version to help check differences.

However, since this is a premium theme I was wondering what are the chances for just resetting the theme. The issue with that is that the site uses shortcodes in the content editor to apply grid layouts (another variable in the issue)…

Still trying to hunt down what makes the site output wonky content, I wish there was a Revision function for when the editor is used in the WP back-end.

Cheers,
Thanks for all the fantastic input. I will deff use child themes for future client projects.

@dimitris33 that seems like the best route, thanks for your help, will be looking into this.

@mike thank you, checking css file diffs were essential to solving this issue, luckily it can be narrowed down to just the css changes. Will update again soon on how this works out.

@jason King, that is a gold-tier suggestion, the child theme concept seems to solve a lot of headaches like this, separating the main theme from the client edits. Haha I can’t stop to laugh about identifying code because I at least somewhat add comments to my code. Also I will look more into revisions for this issue.

Thanks guys, these tips will save me from buying a bottle of aspirin, will update on how it goes but for now I will close it as resolved, thanks again for your time and help!

Hey thanks for replying @dimitris33,

1. changes would pertain to any style changes made to the site, such as CSS changes
2. not sure why exactly I figure the best route was to simply give them our last backup of the site before delivering it to them.
3. client is looking to undo the changes that they had made by themselves.

The big issue with this is that there are transactions going through the site, so I was tasked to bring back our latest backup of the site (to revert back the style changes made), and to add current transactions that the client’s live site has recently made in the database (which I figure may be an issue in itself).

Thanks David,

You were right on, I changed the Domain Name and URL as it says in the link you provided, thank you!