Home › Toolset Professional Support › [Resolved] "Cheating" error when attempting to edit a taxonomy
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Our next available supporter will start replying to tickets in about 5.14 hours from now. Thank you for your understanding.
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
---|---|---|---|---|---|---|
8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
This topic contains 36 replies, has 4 voices.
Last updated by Christian Cox 4 years, 7 months ago.
Assisted by: Christian Cox.
This is an issue that's been happening for a few months now. While troubleshooting, it always circled back to being an Access problem, so I'm contacting you:
There is a custom taxonomy called Art Forms, shared across the post types: Posts, Artists and Events. There are five instances of it, but there is a problem editing one of them - Theater. Whenever I click to edit Theater, and only Theater, I get a cheating error: "Cheatin’ uh? Sorry, you are not allowed to edit this item."
This happens on the highest WP roles: developer (highest) and administrator.
I have provided a Developer-level login for a TEST site on Flywheel, which is available for the next 13 days. This should be the easiest and safest way for you to look over things. If you need to actually download the site onto a local server, do not use duplicator. The Toolset team have a copy of the site that's used for another ticket of mine - please consult with Beda if needed, as he has the copy.
Also, there is a password protection popup window that you will see when you first load the page. I added the user and password for that in the FTP user/password lines below.
Many thanks!
Hello. Thank you for contacting the Toolset support.
First of all - After checking debug information you shared with us, I found that you are using outdated Toolset plugins. We always recommend to run your site with latest stable release plugin version.
*** Please make a FULL BACKUP of your database and website.***
Could you please update ALL Toolset plugins to it's latest official released version. You can download latest plugin release from your accounts page:
=> https://toolset.com/account/downloads/
Also, I see that you are using number of third party plugins that are also outdated and that may also cause the issue. I also recommend to update all third party plugins and try to check by creating new taxonomy term.
I updated all plugins on the test site. Issue still persists. Can you please have another look?
Note: regarding other third-party plugins – they are not the cause, as this happens even when all/most other plugins are deactivated. This is a Toolset Access issue, and keep in mind this happens only for the Theater term, not for any other term.
Well - I checked on your install before as well and I try to create a new taxonomy term and try to edit and it was working perfectly fine and the thing is that I do not see any logical thing that Access deny to access only one specific term "Theater".
There must be some conflict or corrupted database entry.
Is its OK for you then you should try to delete the term "Theater" and try to recreate and and check if that works. If no, then try to deactivate Toolset plugins and check if you able to access the term.
Minesh, it is impossible to delete Theater at this point. It was working fine for over two years. This is a very active site with thousands of users. Please advise.
Well - We do not recommend to debug anything on live site. It will be great if you can setup test server and share access details OR send you site copy to debug things further.
PS: Beda is not available, he is on long vacation.
Minesh, as I mentioned quite a few times on our thread, the login I provided in the beginning of the thread is of the TEST site (hidden link). You can debug there freely.
Well - I told this to double check this because in your previous reply you said that This is a very active site with thousands of users. .
Its always better to double check and make sure there is no communication gap because we were talking about LIVE site and once we start to debug anything can be possible, so its better to be remain alert.
When I said this is an active site, I meant the actual site - aicf.org - but I have provided hidden link for you so you can run your tests. Hope this clarifies.
Yes - thank you for your prompt response.
I see there is post available with same slug "theater" as your taxonomy term "theater":
=> hidden link
I suspect this might be the cause here but this needs super debug.
Also, could you please check htaccess file, is there any rewrite rules there? If would be great if you pass me FTP access as well to check this thing.
I need your site copy to debug this further:
=> https://toolset.com/faq/provide-supporters-copy-site/
Regarding your first comment, there are pages with the same slug for *each* of the artforms, and they work perfectly fine, so that can't be the issue. Example:
hidden link
hidden link
There is nothing special in the htaccess/rewrite rules in regards to this issue. I have triple-checked it with Flywheel directly.
It is a little complicated to give you FTP access at this point. I am not sure if you know Flywheel but their managed WordPress hosting requires quite a few steps in order to let you in. So far, all my inquiries with Toolset were handled without having to give FTP access.
This is the link to a site copy:
hidden link
This is a simplified version which only includes the database sql file and wp-content. This way you can install a fresh WordPress version and simply copy in the files / import the database. Please note that it does not include the uploads folder – as this would cause the site to be over 15 GB. Also, this is a backup from November, but it is essentially the same, for your debugging purposes. Feel free to update Toolset plugins there directly if you need. So far – this version was used successfully by other Toolset supporters, so consider this a valid version of the site.
Another thing - it looks on your profile that your personal operating hours are ending. Are you going to keep looking into this today or only on Monday? This is quite an urgent issue, so I would appreciate if you can make sure this is reviewed during the weekend as well. Please let me know.
Thanks,
Nadav
Ok - thanks for sharing all required information.
Another thing - it looks on your profile that your personal operating hours are ending. Are you going to keep looking into this today or only on Monday? This is quite an urgent issue, so I would appreciate if you can make sure this is reviewed during the weekend as well. Please let me know.
=> Yes - thats correct. I'm about to end my day.
Due to X-mas around the corner we have limited resource available and we will try our best to give you support but unfortunately no one available in weekend.
I will debug this on Monday and will get in touch with you.
Please check this:
https://toolset.com/2017/12/toolset-support-during-the-holidays/
Are there supporters that work today in Eastern USA? I know Christian Cox is on that timezone. Can you please forward this to him to take a look at today?
Christian do not work on Friday. He may get back on Sunday. You may check with Christian on Sunday.
=> https://toolset.com/forums/users/christian-c/
But Shane is available now, I'm assigning this ticket to him and he will help you further.
Thanks Minesh.
Hi Shane, please let me know if you have all the information from the thread or if you need anything else in order to debug.