• Resolved mattiwilde

    (@mattiwilde)


    Hi,

    after updating Nimble, I can not access my existing nimble-pages. I get the error “Forbidden: You do not have permission to access this document.” when try to edit pages by Nimble.
    But I can open the pages with the Gutenberg-editor.

    Any ideas?

    Thanks in advance!!!

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author presscustomizr

    (@nikeo)

    Hello,
    Thanks for reporting the problem.
    Nimble Builder can be used by all users with admin capability.
    Can you confirm that you followed the troubleshooting steps listed here : https://ww.wp.xz.cn/support/topic/%e2%9a%a0%ef%b8%8f%e2%9a%99%ef%b8%8ftroubleshooting-steps-for-nimble-builder/

    TIPS FOR A FASTER RESOLUTION OF YOUR SUPPORT TOPIC
    When you do create your topic, it helps if you include your system info when creating your post. You’ll find them in your WP admin, in Settings > Nimble Builder > System Info.

    Thank you.

    Thread Starter mattiwilde

    (@mattiwilde)

    Thanks Nicolas!

    I have to add, that the page-access for all sub-pages was also forbidden for all visitors, so not only editing was forbidden.

    Now in debug-mode I can access again the sub-pages and also after deactivating debug-mode.

    Problem solved for this time, but this is really scary!

    System-info:

    ### Begin System Info (Generated 2020-06-02 17:26:43) ###
    ———— SITE INFO
    Site URL:
    Home URL:
    Multisite: No

    ———— USER BROWSER
    Platform: Windows
    Browser Name: Firefox
    Browser Version: 76.0

    ———— WORDPRESS CONFIG
    WP Version: 5.4.1
    Language: de_DE
    Permalink Structure: Default
    Active Theme: Twenty Seventeen 2.3
    Show On Front: page
    Page On Front: Start (#5)
    Page For Posts: Unset
    ABSPATH: /var/www/vhosts/elkechudoba.de/httpdocs/wordpress-systemdateien/
    WP_DEBUG: Disabled
    WP Memory Limit: 40MB

    ———— NIMBLE CONFIGURATION
    Version: 2.0.20
    Upgraded From: 2.0.19
    Started With: 2.0.7

    ———— WP ACTIVE PLUGINS
    Coming Soon Page & Maintenance Mode by SeedProd: 5.1.0
    Gutenberg: 8.2.1
    Insert Headers and Footers: 1.4.5
    Menu Image: 2.9.6
    Nimble Page Builder: 2.0.20
    UpdraftPlus – Backup/Restore: 1.16.25
    WP Rollback: 1.7.0

    ———— WP INACTIVE PLUGINS
    Adminimize: 1.11.6
    Akismet Anti-Spam: 4.1.5
    Classic Editor: 1.5
    Cookiebot | GDPR/CCPA Compliant Cookie Consent and Control: 3.6.5
    Duplicate Page: 4.2
    GDPR Cookie Compliance: 4.2.1
    GDPR Cookie Consent: 1.8.8
    Max Mega Menu: 2.8
    Opening Hours: 2.2.1
    Search Meter: 2.13.2
    Shortcode in Menus: 3.5
    User Role Editor: 4.54

    ———— WEBSERVER CONFIG
    PHP Version: 7.4.6
    MySQL Version: 5.7.30
    Webserver Info: Apache
    Writing Permissions: OK

    ———— PHP CONFIG
    Memory Limit: 256M
    Upload Max Size: 128M
    Post Max Size: 128M
    Upload Max Filesize: 128M
    Time Limit: 30
    Max Input Vars: 5000
    Display Errors: N/A
    PHP Arg Separator: &
    PHP Allow URL File Open: 1

    ### End System Info ###

    Plugin Author presscustomizr

    (@nikeo)

    OK. I’m glad you solved.
    But I don’t know what could be the cause of the issue… Nimble Builder woulnd’t limit access randomly like this.
    So switching back and forth the debug mode solved the problem, is that right ?
    Thanks

    Thread Starter mattiwilde

    (@mattiwilde)

    Yes, that is right.

    Thank you!

    Thread Starter mattiwilde

    (@mattiwilde)

    Solved

    • This reply was modified 6 years ago by mattiwilde.
    Thread Starter mattiwilde

    (@mattiwilde)

    Now I see, that it is obviously not caused by Nimble. I had to recover a backup, and have now the same problem without the update. I guess, it is some server-misconfiguration.

    Sorry!

    Plugin Author presscustomizr

    (@nikeo)

    OK thanks for providing those info.

    Thread Starter mattiwilde

    (@mattiwilde)

    Ok, now I know even more and I can reproduce the steps:

    1. recover backup with Nimnble 2.0.15
    2. deleted all placeholder-images and replace them by images with same name
    3. open page with Nimble and access denied for wp-admins and page-visitors
    4. open Nimble in debug-mode, no success
    5. changed permalinks in wp-settings and changed back, and after ca. 5 minutes it worked again, so it is the old familiar permalink- and update-problem, and it was a coincidence that it worked after switching into debug-mode.

    Plugin Author presscustomizr

    (@nikeo)

    👍

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Access forbidden after update’ is closed to new replies.