identify ValueError reason – feature request

  • Saleswonder Team: Tobias

    (@tobias_conrad)


    4 years, 3 months ago

    @timwhitlock Hey Tim,
    you are giving such a nice plugin which is a standard in WP world now for free.

    I myself added some “” in translation and killed my whole plugin during translation.
    I needed a developer to show me what i did wrong. I am now aware and search issue on my side and site first. It is the fastest way to solution too.

    As you Tim have already said, the ValueError shown in your log is in the string. Not in loco plugin.

    How can a non developer find the wrong “” which lead to a ValueError in all the code?

    This would be an awesome feature.

    best regards and unlimited thank yous to you TIM

Viewing 1 replies (of 1 total)
  • Plugin Author Tim W

    (@timwhitlock)

    4 years, 3 months ago

    Validation of printf formatting is already on the TODO list. It has been for a while and I hope to get it into the next release.

    I know you commented on this thread recently but moderators seem to have removed your reply as being a “same here” violation. Hard luck.

    However, I don’t follow how your comment about adding quote marks. Specifically what you did to produce a ValueError. There are many examples of wrong formatting, but can you show me your example?

Viewing 1 replies (of 1 total)

The topic ‘identify ValueError reason – feature request’ is closed to new replies.