• Resolved rockyourblog

    (@rockyourblog)


    Hey,

    since I’ve updated to v5.0 I can’t save existing recipes. Creating new ones works though, but if I open these again, edit something and hit “save” or “save & close” a error message pops up, too.

    I’m using WP v5.2 with PHP v7.3 and have WPRM Premium & Premium Pro Bundle installed and activated.

    Here’s a screenshot: https://imgur.com/a/U0jJN1y

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

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Brecht

    (@brechtvds)

    Hi there,

    Could you check for any errors in the JavaScript console?
    https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors

    Thread Starter rockyourblog

    (@rockyourblog)

    Hi Brecht,

    thanks for your reply!

    The console prints this after hitting “save” button using Firefox. Apart from that, I can’t see anything related to WPRM.

    Response { type: "basic", url: "https://[mysite].com/wp-json/wp/v2/wprm_recipe/18210", redirected: false, status: 403, ok: false, statusText: "Forbidden", headers: Headers, body: ReadableStream, bodyUsed: false }
    admin-modal.js:30:23435

    I disabled the Plugin “All In One WP Security & Firewall” and now it works again. Enabled it and the error shows again. Seems one or more of the .htaccess rules set by this Plugin are preventing WPRM to access the requested files.

    These are the rules pasted by “All In One WP Security & Firewall”:
    https://www.zeta-uploader.com/1869185873

    Maybe you can help me find the culprit here, otherwise I’ll contact support of AIOWPS.

    Plugin Author Brecht

    (@brechtvds)

    It’s a 403 forbidden error, so that firewall seems to indeed be blocking access.

    I’m not sure which one of those rules is causing the problem but it might be possible to exclude calls that include /wp-json/ in the URL.

    I’m having the exact same issue now too. Did you resolve it @rockyourblog?

    I’ve tried white listing the URL in Wordfence security but nothing’s working yet.

    Plugin Author Brecht

    (@brechtvds)

    @lasercosmetics are you getting the 403 forbidden error?
    Feel free to send a screenshot of what you’re seeing exactly to support@bootstrapped.ventures and we’ll have a look.

    Thread Starter rockyourblog

    (@rockyourblog)

    Hey,

    I’ve opened a support thread at AIOWPS forum, but no one has answered yet: https://wordpress.org/support/topic/possible-conflict-between-aiowps-wp-recipe-maker-v5/

    I’ve isolated the problem to the 6G-Firewall rules used by AIOWPS though. If I disable these in my .htaccess, it works again. Maybe Wordfence does use them too?

    Unfortunately turning off parts of the firewall is not really a viable solution to this issue. Maybe one of you guys have an idea wich rule is causing this behavior?

    #AIOWPS_SIX_G_BLACKLIST_START
    # 6G FIREWALL/BLACKLIST
    # @ https://perishablepress.com/6g/
    
    # 6G:[QUERY STRINGS]
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteCond %{QUERY_STRING} (eval\() [NC,OR]
    RewriteCond %{QUERY_STRING} (127\.0\.0\.1) [NC,OR]
    RewriteCond %{QUERY_STRING} ([a-z0-9]{2000,}) [NC,OR]
    RewriteCond %{QUERY_STRING} (javascript:)(.*)(;) [NC,OR]
    RewriteCond %{QUERY_STRING} (base64_encode)(.*)(\() [NC,OR]
    RewriteCond %{QUERY_STRING} (GLOBALS|REQUEST)(=|\[|%) [NC,OR]
    RewriteCond %{QUERY_STRING} (<|%3C)(.*)script(.*)(>|%3) [NC,OR]
    RewriteCond %{QUERY_STRING} (\|\.\.\.|\.\./|~|
    
    |<|>|\|) [NC,OR]
    RewriteCond %{QUERY_STRING} (boot\.ini|etc/passwd|self/environ) [NC,OR]
    RewriteCond %{QUERY_STRING} (thumbs?(_editor|open)?|tim(thumb)?)\.php [NC,OR]
    RewriteCond %{QUERY_STRING} ('|\")(.*)(drop|insert|md5|select|union) [NC]
    RewriteRule .* - [F]
    </IfModule>
    
    # 6G:[REQUEST METHOD]
    <IfModule mod_rewrite.c>
    RewriteCond %{REQUEST_METHOD} ^(connect|debug|move|put|trace|track) [NC]
    RewriteRule .* - [F]
    </IfModule>
    
    # 6G:[REFERRERS]
    <IfModule mod_rewrite.c>
    RewriteCond %{HTTP_REFERER} ([a-z0-9]{2000,}) [NC,OR]
    RewriteCond %{HTTP_REFERER} (semalt.com|todaperfeita) [NC]
    RewriteRule .* - [F]
    </IfModule>
    
    # 6G:[REQUEST STRINGS]
    <IfModule mod_alias.c>
    RedirectMatch 403 (?i)([a-z0-9]{2000,})
    RedirectMatch 403 (?i)(https?|ftp|php):/
    RedirectMatch 403 (?i)(base64_encode)(.*)(\()
    RedirectMatch 403 (?i)(=\'|=\%27|/\'/?)\.
    RedirectMatch 403 (?i)/(\$(\&)?|\*|\"|\.|,|&|&?)/?$
    RedirectMatch 403 (?i)(\{0\}|\(/\(|\.\.\.|\+\+\+|\\"\\")
    RedirectMatch 403 (?i)(~|
    |<|>|:|;|,|%|\|\s|\{|\}|\[|\]|\|)
    RedirectMatch 403 (?i)/(=|\$&|_mm|cgi-|etc/passwd|muieblack)
    RedirectMatch 403 (?i)(&pws=0|_vti_|\(null\)|\{\$itemURL\}|echo(.*)kae|etc/passwd|eval\(|self/environ)
    RedirectMatch 403 (?i)\.(aspx?|bash|bak?|cfg|cgi|dll|exe|git|hg|ini|jsp|log|mdb|out|sql|svn|swp|tar|rar|rdf)$
    RedirectMatch 403 (?i)/(^$|(wp-)?config|mobiquo|phpinfo|shell|sqlpatch|thumb|thumb_editor|thumbopen|timthumb|webshell)\.php
    </IfModule>
    
    # 6G:[USER AGENTS]
    <IfModule mod_setenvif.c>
    SetEnvIfNoCase User-Agent ([a-z0-9]{2000,}) bad_bot
    SetEnvIfNoCase User-Agent (archive.org|binlar|casper|checkpriv|choppy|clshttp|cmsworld|diavol|dotbot|extract|feedfinder|flicky|g00g1e|harvest|heritrix|httrack|kmccrew|loader|miner|nikto|nutch|planetwork|postrank|purebot|pycurl|python|seekerspider|siclab|skygrid|sqlmap|sucker|turnit|vikspider|winhttp|xxxyy|youda|zmeu|zune) bad_bot
    
    # Apache < 2.3
    <IfModule !mod_authz_core.c>
    Order Allow,Deny
    Allow from all
    Deny from env=bad_bot
    </IfModule>
    
    # Apache >= 2.3
    <IfModule mod_authz_core.c>
    <RequireAll>
    Require all Granted
    Require not env bad_bot
    </RequireAll>
    </IfModule>
    </IfModule>
    #AIOWPS_SIX_G_BLACKLIST_END
    • This reply was modified 4 years, 11 months ago by Jan Dembowski.
    • This reply was modified 4 years, 11 months ago by Jan Dembowski.
    Thread Starter rockyourblog

    (@rockyourblog)

    Updating to WPRM v5.0.4 solved the issue for me. Many thanks!

    Plugin Author Brecht

    (@brechtvds)

    Happy to hear!

    We’re now emulating PUT requests by POST requests, so they’re not getting blocked by that rule anymore.

    Do let me know if you experience any other issues.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Can’t edit & save existing recipes’ is closed to new replies.