• Resolved Barry

    (@barrypersonalctonet)


    Trying to get started with the plugin for a site on a multisite installation. Tried to create a publication and got “Publication failed during initialize_crawler task” with urls mentioned and the message: “WordPress database error: Processing the value for the following field failed: url. The supplied value may be too long or contains invalid data.”

    Is there a way to get past this?

    Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Team Staatic

    (@staatic)

    Hi Barry, thanks so much for trying Staatic to improve the performance and security of your WordPress sites.

    According to the error, during the crawler initialization phase (where Staatic builds a list of URLs that should definitely be included in the static version of your site), a URL was encountered which was either too long (longer than 2,083 characters), or contains invalid characters (in most cases non-UTF-8 characters).

    In order to resolve the issue, we need to find out which URL is causing this, and which URL provider provided the invalid URL. Could you please enable “Detailed logging” and restart the publication? Detailed logging can be enabled from Staatic > Settings > Advanced > Logging. Once the publication has finished, you can view the logs by going to Staatic > Publications > Details > Logs.

    Could you then share the last log entries before the publication fails? You may also send an export of the publication logs (using the Export button at the top of the Logs page) as well as a copy of your site’s Health Info report (by going to Tools > Site Health > Info > Copy site info to clipboard) to [email protected]. This will give us a bit more information to work with.

    Looking forward to your feedback.

    Plugin Author Team Staatic

    (@staatic)

    @barrypersonalctonet, is everything up and running for you now? If you’re still having trouble, could you let us know where things stand? We’re ready to assist!

    Plugin Author Team Staatic

    (@staatic)

    @barrypersonalctonet, we just wanted to let you know that we managed to find the root cause of this issue.

    Due to an error in the database schema definition, urls longer than 255 characters were not handled correctly. This has been addressed in the latest plugin release, version 1.6.3. We encourage you to download this version at your earliest convenience.

    Should you encounter any more difficulties or if you have any more queries, please feel free to reach out.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘URL too long?’ is closed to new replies.