Support » Plugin: Elementor Website Builder » Server Error (403 Forbidden) / Deprecated: _register_controls

  • Siren

    (@sirenwatcher)


    Error Message: Server Error (403 Forbidden)
    Plugins: Deactivated all of the plugins. Still occurs.
    Caching plugin: Turned off cache, explunged cache and turned off CDN. Still has issue.
    Themes: Changed theme. Still has same issue.
    WP-DEBUG: Upon editing this, I get this error,
    <em>"Deprecated: _register_controls is deprecated since version 3.1.0! Use Elementor\Controls_Stack::register_controls() instead. in /home/freeside/public_html/sirenwatcher.com/wp-includes/functions.php on line 5323"</em> alongside some pages having the message <em>"Deprecated: Required parameter $linkcount follows optional parameter $onlycount in /home/freeside/public_html/sirenwatcher.com/wp-content/plugins/link-library/render-link-library-sc.php on line 314"</em>
    Htaccess: I have deleted htaccess to make sure it wasn’t corrupted.

    The normal warnings are repeated in the PHP_Log:

    [04-May-2022 10:01:59 Europe/Amsterdam] PHP Warning:  Constant AUTH_SALT already defined in /home/freeside/public_html/sirenwatcher.com/wp-config.php on line 79
    [04-May-2022 10:01:59 Europe/Amsterdam] PHP Warning:  Constant SECURE_AUTH_SALT already defined in /home/freeside/public_html/sirenwatcher.com/wp-config.php on line 80
    [04-May-2022 10:01:59 Europe/Amsterdam] PHP Warning:  Constant LOGGED_IN_SALT already defined in /home/freeside/public_html/sirenwatcher.com/wp-config.php on line 81
    [04-May-2022 10:01:59 Europe/Amsterdam] PHP Warning:  Constant NONCE_SALT already defined in /home/freeside/public_html/sirenwatcher.com/wp-config.php on line 82

    System info:

    Operating System: Linux
    Software: LiteSpeed
    MySQL version: MariaDB Server v5.7.37			
    PHP Version: 8.0.18		
    PHP Memory Limit: 512M
    Write Permissions: All right
    WordPress Environment Version: 5.9.3
    Memory limit: 128M
    Theme: Blossom Chic

    F12 dev results:
    https://paste.ubuntu.com/p/3sX85Th6XF/

    • This topic was modified 7 months ago by Siren. Reason: spelling
    • This topic was modified 7 months ago by Siren.

    The page I need help with: [log in to see the link]

Viewing 10 replies - 1 through 10 (of 10 total)
  • Hi,

    Do you recieve the 403 error when trying to submit changes on your page?

    If so, this issue can also be due to the firewall of your server. Ask your hosting company to disable any firewall or ModSecurity and check if it helps.

    Thread Starter Siren

    (@sirenwatcher)

    They claim it is not a firewall error. This was one of the first things I asked them. Yes it is when submitting changes on posts.

    • This reply was modified 6 months, 4 weeks ago by Siren.

    Hi,

    Please try to downgrade the PHP version to 7.3/7.4 and let us know if that makes a difference

    Thread Starter Siren

    (@sirenwatcher)

    It was changed from PHP 8 to PHP 7.3 and had no effect.

    Hi,

    Since Error 403 is a server issue (responses when something is forbidden from accessing some resource), your hosting provider should check this from their end.

    You may also send us your access logs and PHP error logs so we could check them.

    Thread Starter Siren

    (@sirenwatcher)

    Please read the first post as to your request.

    Hi,

    It seems to be incomplete Error logs since the logs are older. Some hosting companies store the PHP Error logs in two places -> One is accessible via cPanel (or alternative) and the second one is accessible via File Manager and it should be called error log.

    You may also generate a WP Debug log for us by inserting this code to the wp-config.php file in the root folder of their WP installation:

    define( ‘WP_DEBUG’, true );
    define( ‘WP_DEBUG_DISPLAY’, false );
    define( ‘WP_DEBUG_LOG’, true );

    Thread Starter Siren

    (@sirenwatcher)

    Please read the initial post correctly and give a human response. Any human reading the first message would not have sent the last two messages. “You may also generate a WP Debug log” is totally redundant and it severely makes me think your product isn’t actively being supported as your answer is clearly a macro written possibly by a bot.

    “It seems to be incomplete Error logs since the logs are older.” the code log written and the F12 report written was taken a week ago. On the day I made the post. No offense, but again, a human would have easily been able to see that and a macro bot wouldn’t be programmed to read that. If you don’t have proper time to respond more rapidly, do not then critique the times of upload.

    My questions for the simple AI algorithm:
    1. What does this mean: “PHP Warning: Constant AUTH_SALT already defined in /home/freeside/public_html/sirenwatcher.com/wp-config.php”

    • This reply was modified 6 months, 3 weeks ago by Siren.

    Hi Siren,

    Please mind the forum guidelines: “Above all, users are expected to be kind, helpful, and respectful. Assume the best of people and try to make things better”. ref: https://wordpress.org/support/guidelines/

    Regarding your question:

    AUTH_SALT defines a salt -> random data/string used as an additional input to a one-way function that hashes data. The PHP Warning: Constant AUTH_SALT already defined in” means exactly what is written here, they have it defined twice in their WP Config. It may help you, but it should not cause the 403 error by itself.

    Thread Starter Siren

    (@sirenwatcher)

    In regards to the guidelines, please adhere to these rules to be better and be less dismissive towards the fallacy in your argument. Ie, you were rude to the customer. Please do not make this mistake again by disobeying the guidelines set down by wordpress that you should respect customer complaints. You should be respectful towards customers who spend their time providing answers and not be rude towards their intention at being efficient. I get that maybe elementor is horribly run and has no efficient support staff, but I hope in the future the support improves and you make things better for customers. By improving the internal guidelines for what constitutes as support, by actually reading customer questions thoroughly and not breaking wordpress guidelines by being ignorant and dismissive towards forum questions. It seems odd to have put the link in this thread, as you were clearly the one disobeying the guidelines, but whatever you feel is appropriate for your concerted effort in providing appropriate levels of non-AI support.

    From what I understand from the strings is that they mean nothing. They do not specify a problem. Which is what I gather from what you have said. It is showing that data has been hashed but that it means nothing specifically in itself. Which is why I am concerned at why you want the log data. As it doesn’t say anything except these same errors (and possibly this is common, very occasionally maybe it provides errors which is why you asked but I have no idea if its just a redundant question because it wasn’t specified as to why elementor wants the details).

    WP-DEBUG seems to open up and provide specific errors, which is why i provided it initially. Debug seems more useful in having you address the situation individually.

    Ie, it seems there is a conflict with link library and elementor. I have no idea why you didn’t know that after an entire week of “research” and 5 responses. Could you please actually look into the error messages I provided.

    “`You may also generate a WP Debug log for us by inserting this code to the wp-config.php file in the root folder of their WP installation:

    define( ‘WP_DEBUG’, true );
    define( ‘WP_DEBUG_DISPLAY’, false );
    define( ‘WP_DEBUG_LOG’, true );`”

    There would be no way I could have provided the WP-Debug without doing that in the original post obviously. As the error messages would have been hidden by default. Please offer genuine answers in the future and speak in a more humanistic way that looks to solve consumer issues.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Server Error (403 Forbidden) / Deprecated: _register_controls’ is closed to new replies.