WordPress.org

Ready to get started?Download WordPress

Forums

Hyphenator
Vers. 4.1.0 insecure? (20 posts)

  1. Gerhard Lichtenauer
    Member
    Posted 1 year ago #

    After having updatetd to vers. 4.1.0 following error occurs on the blog-site: "Hyphenator.js says: An Error occurred: The operation is insecure."

    http://wordpress.org/extend/plugins/hyphenator/

  2. tomppa28
    Member
    Posted 1 year ago #

    Hello,

    I encountered the exact same problem, and I regret that the extension has become unusable. Will there be an update ?

    Thx in advance,

    Thomas

  3. Gestroud
    Member
    Posted 1 year ago #

    I'm experiencing the same problem on a new WP 3.4.2 installalltion.

  4. kravallle
    Member
    Posted 1 year ago #

    same for me.

  5. Gerhard Lichtenauer
    Member
    Posted 1 year ago #

    Since there is no bugfix yet, I reinstalled vers. 4.0.0 and this works.
    downloads.wordpress.org/plugin/hyphenator.4.0.0.zip

  6. sfbarth
    Member
    Posted 1 year ago #

    I have the problem only where the domain name entered doesn't match the name stored in WordPress. Like, wordpress is installed in xyz.de, but the xyz.com points to the same directory. Seems like a security measure to me. If that's the case, it would be neat to have an option to enter 'legal' domain names.

    Strange: in Hyphenator_debug.js the alert is triggered on line 342 (v. 4.1.0)
    onError = function (e) { window.alert ...
    in the Hyphenator.js it seems to turn into
    b=function(t){e.alert( ... on line 61

    I don't know enough javascript - none, really ;-) - to make sense of this.

  7. Benjamin Pick
    Member
    Posted 1 year ago #

    The maintainer said at https://code.google.com/p/hyphenator/wiki/en_reportProblems:

    > This sounds like a same-origin-policy issue. Do you have a link or test case where I can reproduce the problem?
    > Some Error-logs could help, too…

    For the wordpress extension, I'd suggest an option "surpress all error messages for non-logged-in users" (- happy to supply a patch if needed). In this way, at least the user doesn't realize something went wrong.

    (Just pass "onerrorhandler: function() {}," as an option to the Hyphenator object. Alternatively, allow "advanced options" to be set - see also patch at http://www.nomachetejuggling.com/2011/05/23/adding-dont-hyphenate-class-name-support-to-hyphenator/)

  8. Benjamin Pick
    Member
    Posted 1 year ago #

    Oh, I've found a workaround: just put the following text into the "minimal word length"-option:

    7, onerrorhandler: function() {}

    Quite a hack, but it allows to add custom option (as the options are not validated/escaped). (Keeping the default of 6 does not work, though.)

  9. Benjamin Pick
    Member
    Posted 1 year ago #

    Oh, I see the issue is fixed there (#164 / rev1128). So the issue will disappear on the next release.

  10. theV0ID
    Member
    Posted 1 year ago #

    Hi, do I understand correctly that this problem should actually have been fixed by now? I'm asking because I'm still having it.

  11. Benjamin Pick
    Member
    Posted 1 year ago #

    Yes and no: it is fixed in the "nightly builds"-Version of it, so if you check this option it should be gone. But No, there has not been a bugfix release yet.
    Alternatively, use my workaround above.

  12. theV0ID
    Member
    Posted 1 year ago #

    Many thanks, choosing the developer-version solved the problem for me. How ever, your workarround didn't.

  13. Gerhard Lichtenauer
    Member
    Posted 1 year ago #

    For me the same error occurs with the developer-version. Once again back to vers. 4.0.0.

  14. e2b
    Member
    Plugin Author

    Posted 1 year ago #

    TL;DR: If the problem occurs to you, please downgrade to version 4.0.0. I'll update this plugin as soon as a fixed version is released by the Hyphenator.js developer. You might also think about your site's domain configuration.

    Sorry for not responding to this thread. I'm not actively maintaining this plugin since I stopped using WordPress and also couldn't really test it. As you likely noticed this plugin just uses the JavaScript "Hyphenator.js" which does the hyphenation work. It seems like a problem there that is not related to my code.

    This really seems related to some same origin policy which will be an issue if the url in the browser address bar differs from the url that is set in the WordPress configuration and used for embedding the JavaScript resource file. Can you confirm this only happens in this special case?

    Besides from the nasty error message, this setup isn't recommended. WordPress sites should only be available using a specific domain. If you would like to use multiple domains for your site, please think about having a default domain and redirecting the others to that one. This is also bad in case of SEO, since Google might vote your site down because of the misuse of multiple domains and making the same content available on multiple sites using different domain names.

    Even I stopped maintaining this plugin, I would like to update it when a fixed version of Hyphenator.js is released. So this plugin should work at least as long as future WordPress versions won't break any used APIs.

    @Benjamin Pick: Nice hack. I plan to add an option for directly writing the configuration code in the next version.

    @sfbarth: The file with the debug suffix is the raw source code used for development, the normal file used by the plugin is a highly size optimized version using short variable names, less whitespaces etc. It does exactly the same and provides the same results even it has a different look.

  15. Pololu
    Member
    Posted 1 year ago #

    I seem to have the issue where the origin seems to be the same for both but I still get the error.

    WordPress Address: http://localhost/wordpress
    Site Address: http://localhost/wordpress

    And the plugin adds the following script source:

    <script type="text/javascript" src="http://localhost/wordpress/wp-content/plugins/hyphenator/Hyphenator.js">

    Rolling back to 4.0 for now.

  16. Pololu
    Member
    Posted 1 year ago #

    Actually, the developer trunk fixed the issue for me. Thanks!

  17. Benjamin Pick
    Member
    Posted 9 months ago #

    @e2b:
    The Version 4.2.0 of the upstream Hyphenator is out now.

  18. Gerhard Lichtenauer
    Member
    Posted 8 months ago #

    @e2b: did you note Benjamin Picks hint?

  19. Gerhard Lichtenauer
    Member
    Posted 8 months ago #

    Is anybody here?

  20. Gerhard Lichtenauer
    Member
    Posted 5 months ago #

    @e2b: show a sign of life, please ...

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.