Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Of course we do fully support Wordpress as a CMS target in Croppy

Creating the user and application Password

We recommend that you create a separate user that only has the roles to manage media.

After creating the user, or selecting an existing one, go ahead and create an application password. This password then needs to be copied into the settings. Make sure to use the username of the user, not the email and also not the name of the application password.

Enter the Username in the User field and the Application Password in the Password field.

The test should now be successful.

Troubleshooting

Images not shown in Wordpress after cropping

We experienced some issues with Hostingproviders where your Website is available via www.- and non www.- URLs. For example https://www.seadev-studios.com and https://seadev-studios.com.

In those cases we had to switch to the www.- URL in order for it to work.

Access Problems when using Plesk

If you are getting errors when using Plesk, this is most likely caused by the Web Application Firewall for the given Webspace.

Checking the Logs, go to your Domains → Web Application Firewall → Error Protocol

In case there is an error, you should see it in there.

You should also see the id of the error. In this case, the error id is 225170, which blocks out api access to the users route, and this causes the error.

To fix it, add the id to the exception list

Hit OK and Test the connection again the Croppy Admin.

  • No labels