Search results

WPTK team has a plan to improve this behavior to support any allowable WordPress file structure customization including changing the location of the wp-content folder. Stay tuned for updates =)

Yep, common operations should work properly because WP installation has been registered. But there are some security measures like "Forbid execution of PHP scripts..." and "Enable hotlink protection" stops working because they expect wp-content directory. Also features like cloning, copy-data...

It is a known limitation, nowadays, WPTK can find WordPress installation if a folder: contains wp-content folder; contain wp-includes folder; contain the wp-config.php file in the current or parent directory. Any other file structure cannot be recognized as WordPress installation. This...

This file contains only records about the errors themselves. Sorry, I meant debug logs that describe how Apache processes a request. https://httpd.apache.org/docs/2.4/mod/mod_rewrite.html#logging https://stackoverflow.com/questions/9632852/how-to-debug-apache-mod-rewrite There should be...

@Xav2c, could you share debug logs of these redirections? It can help to determine which rules affect http requests.

Looks like a bug, we will improve this scenario in near time. Thanks for flagging.

At this time, WPTK can install a new WordPress only with default settings via a service plan during subscription creating. Could you please post this idea on wp-toolkit uservoice? It would be nice; WPTK team picks new ideas from there.

Could you please post this idea on wp-toolkit uservoice? It would be nice; WPTK team picks new ideas from there.

Do you mean that Smart Update should be automatically activated for all new WordPress installations by default? Could you explain that idea, how it should work(or provide use cases)? Nowadays, WordPress Toolkit already adds corresponding "limits" to Service Plans.

Do you want to fix "broken" state of installations, detach all of them, or something else? Each installation can have its own issue that makes it "broken" and should be fixed individually. "broken" means something went wrong when WPTK interact with the installation via wp-cli. After fixing the...

@CercamiFacile cli command is able to detach only one installation per call. If these installations are shown in UI, you can use a filter (located on the top right) then use bulk detach.

Thanks for your report, we faced with this error too. We have been updating WP-CLI to v2 and it will be available in the next release of WordPress Toolkit (5.2.3).

Newer versions of WordPress require newer php versions. This polyfill is required for compatibility with the new version of WordPress. There is no way back, this is caused by a change in the method signatures in the wordpress itself: Code Modernisation: Introduce the spread operator in...

At the moment, this is impossible to do. The whitelist of domains includes only the domain of the site and google.com, and is not available for manual configuration. The only workaround is to add directives ("Additional Apache directives"/"Additional nginx directives" in the web server...

No, It is impossible. RSS-feed readers do exactly what "Hotlink protection" protects from: they display images (from your server, "wp-content/uploads/" directory) on a third-party resource.