Navigation überspringen

[Gelöst] Wordfence is disallowing the import of a module

Dieser Thread wurde gelöst. Hier ist eine Beschreibung des Problems und der Lösung.

Problem: I am unable to successfully import Layouts modules because I am shown a 403 Wordfence security error.

Solution: Make sure all instances of WP hosted in your Control Panel have Wordfence disabled.

Relevant Documentation:
https://wordpress.org/support/topic/need-to-install-wordfence-on-all-the-domains-on-root/

This support ticket is created vor 6 Jahren, 5 Monaten. There's a good chance that you are reading advice that it now obsolete.

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.

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)

Dieses Thema enthält 7 Antworten, hat 2 Stimmen.

Zuletzt aktualisiert von alexG-4 vor 6 Jahren, 5 Monaten.

Assistiert von: Christian Cox.

Author
Artikel
#954509

I have created a new WP site - versteckter Link - and want to replicate the design of an existing site - versteckter Link

I've installed all the same plugins as on the original site, and created a Module containing all the Layouts of the original site.

When I try to import that Module (see image)
versteckter Link

I get this message from Wordfence:
versteckter Link

I tried de-activating ALL plugins (including Wordfence) except the Toolset plugins - but I get the same results.

I've even deleted WordFence, but it's still exerting it's influence and giving me the same message!

I've tried this using the default 2018 Theme, AND with my Child theme of the Starter Theme.

Finally, I deleted the newly-created WP installation, and re-installed everything EXCEPT WordFence ... and get EXACTLY the same message.

Seems spooky to me!

Thanks

Alex

#954598

Hi, it sounds like a caching issue if you're deactivating Wordfence and yet still seeing a Wordfence 403 message. Let's try these troubleshooting steps first:
- Deactivate the non-Toolset plugins once more for testing.
- Make sure caching systems that might not exist in the plugins folder, like advanced-cache.php, are also deactivated.
- Clear your browser cache and cookies, then log back into the wp-admin area.
- Try to import the modules once again.
- If the problem still occurs, try a different browser like Firefox or Chrome instead of the one you are currently using.
- If the problem is still occurring, please upload your modules somewhere like Dropbox or Drive so I can download them and run some tests locally. Provide a download link here and I will take a look.

#954617

Thanks, Christian - all good suggestions. I tried it in a different browser (Firefox), with the same results!

Here is the file I'm using:

versteckter Link

Also, I noticed that the files DO get uploaded. There are now multiple copies of them in folders such as:

public_html/injeenius.com/wp-content/_modulemanager_tmp_/1532449800.5b575408717df/dd_layouts

This is the contents of the above folder:

versteckter Link

Can I just move those files into an appropriate folder? I've seen an obvious place to put them.

Alex

#954629

... In my last statement, I meant to say "I've NOT seen an obvious place to put them"!

#954654

I've also just tried doing a Layouts Import - using Firefox.

It reads the files OK, but then hangs up.

See

versteckter Link

Alex

#954659

Okay thanks, no problems here importing those modules locally so there must be something else going on. May I log into your wp-admin area and server FTP to take a look? Private reply fields are active here.

#954735

Not seeing anything unusual here, your wp-config.php file and your .htaccess file look okay. Please check this document and follow the instructions to access more information about these errors by logging in to your control panel:
https://www.siteground.com/kb/403_forbidden_error/

Let me know what you find out from the error logs.

#954767

Thanks Christian.

I found the problem. Oh my!.....

I had to uninstall WordFence from a completely DIFFERENT WP installation within the same cPanel!!

It seems that WF has a component that operates independently of WordPress and it can effect addon domains within cPanel.

This is where it's explained.

https://wordpress.org/support/topic/need-to-install-wordfence-on-all-the-domains-on-root/

The guy is blaming the bad design of how cPanel works. Be that as it may, if you write software to operate an in environment, you take into account all the quirks in that environment!

Thanks for your efforts, Christian.
Something learned, at least.

Alex