URL too long for log entry or contains invalid data

  • Resolved Gal Baras

    (@galbaras)


    2 years, 4 months ago

    Related to this topic, which is now closed for replies.

    Since Trac ticket 32315 is now resolved, the error message is visible, and it’s time to fix it:

    Failed to insert log entry: WordPress database error: Processing the value for the following field failed: url. The supplied value may be too long or contains invalid data.

    Unfortunately, there is no context information, so it’s difficult to know where this is happening or why. iThemes team, please find this bug and squash it for good. Consider running it through mysql_real_escape_string(), extending the database column to accommodate longer values and/or truncating the value before insertion.

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

Viewing 15 replies - 1 through 15 (of 18 total)
  • Plugin Support chandelierrr

    (@shanedelierrr)

    Hi @galbaras, may I know if your iTSec plugin is up-to-date?

    Thread Starter Gal Baras

    (@galbaras)

    Sure is ??

    Plugin Support chandelierrr

    (@shanedelierrr)

    Hi @galbaras, thank you for confirming, and apologies for the delayed response. As I couldn’t replicate the same issue on my test site, I have submitted a bug report for this. Once I receive feedback from our developers, I will get back to you.

    Thread Starter Gal Baras

    (@galbaras)

    Any updates?

    Thread Starter Gal Baras

    (@galbaras)

    @shanedelierrr Can you please follow up on this? It’s been 2 months.

    Thread Starter Gal Baras

    (@galbaras)

    Anything?

    Plugin Support chandelierrr

    (@shanedelierrr)

    Hi @galbaras, unfortunately, I still haven’t received a response from our developers regarding this issue. Rest assured, I’ll get back to you once I have feedback. I appreciate your patience.

    Plugin Support chandelierrr

    (@shanedelierrr)

    Hi @galbaras, I just received a response that this is definitely included on the list of pending issues. However, there’s no definite ETA for when we will implement the fix. I appreciate your patience!

    Thread Starter Gal Baras

    (@galbaras)

    Any chance you can follow up for me?

    Thread Starter Gal Baras

    (@galbaras)

    Still nothing?

    Thread Starter Gal Baras

    (@galbaras)

    5 months and counting. Last recording instance: 24 November, 2022, but no mention of a fix in the changelog. Has this been fixed?

    Thread Starter Gal Baras

    (@galbaras)

    Has this been resolved yet? It’s been 6 months ??

    Thread Starter Gal Baras

    (@galbaras)

    @shanedelierrr After 7 months, this has yet to be resolved. I’m still getting these messages, despite having a release since the fix was promised and not having any updates for the last 3 months!

    Plugin Support chandelierrr

    (@shanedelierrr)

    Hi @galbaras, apologies for the delayed response. Per our developers, it’s hard to say why this issue is occurring, and it could be related to the hosting/database setup. Could you also relay the issue to your hosting provider and ask their thoughts? We are working on making the error message more informative for this issue, which is already on our to-do list (just low priority at the moment). I sincerely apologize as this might not be the answer you’re looking for, and thank you for being patient.

    Thread Starter Gal Baras

    (@galbaras)

    In my case, I doubt very much that hosting is imposing any limits. It’s most likely that the URL being processed is very long, and needs to be shortened to the length of the column into which it will be inserted.

    This may be low priority, but over 7 months?

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘URL too long for log entry or contains invalid data’ is closed to new replies.