Forums

Global translator: file name too long causes error (1 post)

  1. galbaras
    Member
    Posted 2 months ago #

    I'm getting the following global translator related messages in my PHP error log:

    [14-Sep-2009 02:17:42] PHP Warning:  fopen(/home/plastic2/public_html/themotivationalspeaker/wp-content/gt-cache/nl/_index.php_nl_motivational-presentations_communication-and-relationships_different-strokes-for-different-folks_gltr_redir=http___translate.google.com_translate_hl=en&sl=en&tl=nl&u=http%3A%2F%2Fwww.themotivationalspeaker.biz%2Findex.php%2Fmotivational-presentations%2Fcommunication-and-relationships%2Fdifferent-strokes-for-different-folks) [<a href='function.fopen'>function.fopen</a>]: failed to open stream: File name too long in /home/plastic2/public_html/themotivationalspeaker/wp-content/plugins/global-translator/translator.php on line 1145
    [14-Sep-2009 02:17:42] PHP Warning:  flock() expects parameter 1 to be resource, boolean given in /home/plastic2/public_html/themotivationalspeaker/wp-content/plugins/global-translator/translator.php on line 1146
    [14-Sep-2009 02:17:42] PHP Warning:  fwrite(): supplied argument is not a valid stream resource in /home/plastic2/public_html/themotivationalspeaker/wp-content/plugins/global-translator/translator.php on line 1150
    [14-Sep-2009 02:17:42] PHP Warning:  fclose(): supplied argument is not a valid stream resource in /home/plastic2/public_html/themotivationalspeaker/wp-content/plugins/global-translator/translator.php on line 1152

    Possible solutions:

    1. Using a filename conversion table, instead of coding the entire URL in the file name
    2. Using a relative URL in the filename
    3. Using category IDs instead of names
    4. Using post IDs instead of permalinks

    Thank you,
    Gal

Reply

You must log in to post.

About this Topic