Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor fireproofsocks

    (@fireproofsocks)

    Next version will address this (there is a feature request already: note that I don’t consult the forums as a guide to development). Unfortunately WordPress makes dealing with paths incredibly difficult because it does not offer configurations or functions for determining paths of critical parts of the app — it’s the only CMS I know of that omits these features, so the CCTM has to work around the limitations.

    There is an FAQ to assist in migrations.

    If you want to see features implemented more quickly, please make a donation.

    Thread Starter benerwin

    (@benerwin)

    Thanks for your reply.
    Everytime I have needed the server path for in a plugin, I have obtained it in PHP.
    It’s a simple matter, unless I’m missing something.
    $_SERVER[‘DOCUMENT_ROOT’] is your friend.

    Plugin Contributor fireproofsocks

    (@fireproofsocks)

    Unfortunately, it’s not that simple: WordPress can be installed in a subdirectory, so justing knowing the path of current script doesn’t tell you where the WP app is or where it is relevant to the web root (i.e. the URL).

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Stop using full paths in meta data please’ is closed to new replies.