Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter LaKing

    (@laking)

    wait wait .. 🙂 …

    Since I use the same wordpress folder for several instances, I slightly modified wp-load.php, as I had to insert something that distinguishes between instances, the sites. To achieve the desired functionality I use $_SERVER[‘DOCUMENT_ROOT’], and that returns the entry from the apache config file, which is a symlink.

    In clear-text, since we have the possibility of symlinks $_SERVER[‘DOCUMENT_ROOT’] and __FILE__ are not necessarily in the same ‘area’ with their return vaules so to say. They might be symlinked paths across the filesystem.

    We can overcome this, with the convention, that we use absolute symlink-free real path’s, eg.: realpath($_SERVER[‘DOCUMENT_ROOT’]).
    “Since PHP 4.0.2, __FILE__ always contains an absolute path with symlinks resolved …” so we need to have an eye on ‘$_SERVER’ and other functions that may return symlinks …

    .. every day something to learn. 🙂 …

    Thread Starter LaKing

    (@laking)

    Okay, I figured ot what the problem was. My fault.
    Actually the whole js folder was told to be under a non-existing URL (some wicked url-path-mix instead …)

    I use some symlinks in my configuration, and due to that plugin_basename() did not return the proper path. I could correct that errror simply by placing a PHP realpath function in wp-load.

    Strange that other plugins never used the plugin_basename() function.

    Thank you for your help. Now I look forward to test the plugin properly.

    🙂

    Thread Starter LaKing

    (@laking)

    .. by the way, the “Insert Saved Form” button seems to be functional.

    Thread Starter LaKing

    (@laking)

    I’m using firefox 3.6.17 with Fedora 14. I also tested it under a virtual Win 7 with IE8. Same behavior.

    I have/had qTranslate, that could be probably in relation.
    However, same behavior with all plugins deactivated, even deleted, and after clearing browser cash, history, cookies. …

    On the server the wp files are write-protected. I can’t even determine if the bug is on server or client side, looks like a compatibility issue.

    I try’d also with a wp instance that never saw any other plugins.

    There is an elegant solution for this.

    /themes/piano-black/index.php
    Line 28, 155th character.

    You see comments_popup_link function from wordpress has 3 arguments given, each of them functions. However this function takes 5 arguments.
    The 4th is a CSSStyle, the fifth is the responsible closed option.

    So simply extend, let 4th argument be 0, and fifth an empty string.
    so it looks like this at the end:
    .. piano-black'),0,''); ?>
    That should do the trick. The most proper solution is to write a __(); function here tho …`

    Thread Starter LaKing

    (@laking)

    .. thanks fro the plugin, great one. Thanks for WordPress. Thanks for linux. Thanks for opensource. ..

    Thread Starter LaKing

    (@laking)

    Okay, .. seems it was some loal problem.

    One can never clear the cash – trash often enough.

Viewing 7 replies - 1 through 7 (of 7 total)