• With the latest version (WP 3.2.1 / CCTM 0.9.4) activated, I get: Warning: is_writable() [function.is-writable]: open_basedir restriction in effect. File(/) is not within the allowed path(s): (/nfs:/tmp:/usr/local:/etc/apache2/gs-bin) in /nfs/c04/h02/mnt/12345/domains/xyz.org/html/wp/wp-admin/includes/misc.php on line 133

    Deactivate it and site works as expected. Sorry, but site is in development so can’t post link.

    http://ww.wp.xz.cn/extend/plugins/custom-content-type-manager/

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

    (@fireproofsocks)

    Aha… the open_basedir is a PHP error that has to do with your server settings. The plugin attempts to create a directory where it can store definition files (and some other things are slated for future storage). I’d love to tinker with this on your server if you’re willing to provide me FTP access. If that’s not an option, my guess is that the following will fix the error:

    1. FTP to your site
    2. Navigate to your wp-content/content/uploads directory
    3. Create a directory named cctm
    4. Go inside that directory, then create a sub-directory named defs

    The plugin attempts to create those directories if they aren’t there, but it looks like it’s failing. This might be representative of a permissions problem larger than the CCTM plugin. What are the permissions on your wp-content/content/uploads directory?

    Thread Starter Peter Hardy-vanDoorn

    (@petervandoorn)

    I have changed my upload directory in WP’s Media settings. Would that cause the problem?

    The new directory is /assets and has permissions of 755.

    There is also a vestigial /wp-content/uploads directory with permissions of 755.

    There is not a /wp-content/content/uploads directory though.

    Where should I create the required cctm/defs directories and what should their permissions be?

    Finally, the old version of your plugin didn’t exhibit this problem, and I do have others that also create directories that don’t seem to have this problem.

    Thanks for all your help

    peter

    Plugin Contributor fireproofsocks

    (@fireproofsocks)

    Sorry, you’re right: it should be /wp-content/uploads — I mistyped. Yes, changing the uploads directory would cause problems — this should be a feature request to make CCTM read from the Media settings for where to store files. Version 0.9.3 didn’t make as much use of that directory, so there was less possibility of a problem.

    Could you file this as a bug in the bug tracker? Thanks!

    Plugin Contributor fireproofsocks

    (@fireproofsocks)

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

The topic ‘[Plugin: Custom Content Type Manager] Latest version broken ?’ is closed to new replies.