New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃敆 馃摎 馃悶 Bug Report: Elementor PRO 3.16.2 breaks WP-TOOLKIT again like in (Related to #21431) #24063
Comments
Issue confirmed. Never seen any plugin breaking WP Toolkit in such a way before. That is a major problem and loss of time as a hosting provider. A quick fix would be much appreciated. |
Your Tier 2 technical support wrote "After thoroughly examining your website, I can confirm that the issue you are experiencing is related to the third-party plugin PLESK WP Toolkit. I regret to inform you that, as per our support policy, we cannot provide technical assistance for third-party themes, plugins, and custom codes." - sorry i dont confirm 馃憥 |
Plesk's WP Toolkit team is supposed to be in touch with Elementor team as said in the Plesk group on Facebook. That is probably the way to go for this... |
Yeah, I ran into this issue on few sites I created and I host. I thought that it was Plesk's WP Toolkit bug. Sorry, but nope. It was issue with my code. After fixing my code, everything is ok. Double check your theme files and custom codes. |
Quick Fix File: elementor-pro/core/editor/editor.php ${package} is deprecated. |
maybe you had another bug... fix from @Paradinight worked great! |
Thanks alot! That fix did the trick, even Elementor Support still tells me, its a WP Toolkit bug and they can not help.... really disapointing. Hope they will build in that fix asap... |
So in the end there is an actual error in Elementor, but I still wonder... How can it affect WP Toolkit unless it has structural deficiencies that can let it be affected by WordPress's plugins? |
@UltimateByte WP Toolkit has the display_errors active and shows all errors, warnings and notice. https://www.php.net/manual/en/errorfunc.configuration.php#ini.display-errors |
Yes OK but it prevents login to WP admin in some contexts... So it's not only a matter of displaying errors but also its behavior is affected somehow. |
When wil this get fixed? as I think it's now proven that the bug is with elementor. |
I am interested to, but as i gut other errors and elementor support always tells me its the problem of others and they can not support other plugins, i guess it will take ages... sorry but that support should shame for naming it support :-/ |
I talked with Elementor Techinical Support today and they pointed the finger at WP Toolkit as the problem again. Very frustrating that they will not fix their software and update their deprecated code. |
Haha, as i said, their support has no plan! And the developers seem not to care, even it is only 1 line to fix and the fix is already clear... |
@furchtlos76 Maybe try to make the pull request with the fix? |
Sorry i am no coder and dont even know what this is at github. Maybe @Paradinight who found the fix, could do that? |
@furchtlos76 I was up to do it, but in fact, my bad, Elementor Pro is not publicly on Git so we can't even do that. |
God thanks Plesk fixed the bug elementor should fix, as here none seems to care, even of such easy to do fixes. Whats up?! |
@furchtlos76 Elementor Pro 3.18 Beta has the fix. |
Prerequisites
Description
Elementor Elementor Pro 3.16.2
When using using Wordpress tookit in PLESK, it throws this error when trying to use "login to wordpress" like in Bug Report #21431 but in WP Toolkit for PLESK and only affecting when Elementor PRO is active!
"Error getting administrator credentials: An error has occurred when decoding JSON: illegal Token"
If disabling elementor PRO and only let elementor active, problem goes away. Going back to php 8.1 or 7.4 fixes the problem too!
Steps to reproduce
Use PHP 8.2.1 for a Domain (some report they had the problem when updating to 8.1. - i directly gone to 8.2.1)
Try to login to Wordpress via WP-Toolkit in PLESK there are several reports in Plesk, too like:
https://support.plesk.com/hc/en-us/articles/13302778467991
https://talk.plesk.com/threads/error-getting-administrator-credentials-illegal-token-when-decoding-json.368755/
Isolating the problem
System Info
Click to reveal
The text was updated successfully, but these errors were encountered: