• Resolved riverie

    (@riverie)


    Hi folks,
    This has appeared on a site that was functioning fine before.
    It was on a multi site installation and imported as a single site using WP Importer, functioned fine after that.

    I have disabled plugins and changed to default wp theme 2016, however problem still there.
    Site address and wordpress address are the same.
    Has anyone any ideas on what may have caused, I know from other forum posts its normally either a plugin or site address issue.
    Thanks
    Ian

Viewing 9 replies - 1 through 9 (of 9 total)
  • Hello, Ian, & welcome to the WordPress support forum.

    I’m afraid right now I have more questions than answers, but your answers, in turn, may well lead us to the nature of the problem.

    So, w/that said:
    * Could you please provide us w/your site url?
    * What sort of hosting are you on–shared? VPS? Dedicated?
    * What operating system is your site hosted on, i.e., Linux or Windows?

    Also, could you please post your wp-config.php ***being sure to remove your credentials*** & your .htaccess file.

    I think that’s it for now. I hope you’ll reply so we can assist. Looking forward to hearing back from you.

    Hello, Ian, & welcome to the WordPress support forum.

    I’m afraid right now I have more questions than answers, but your answers, in turn, may well lead us to the nature of the problem.

    So, w/that said:
    * Could you please provide us w/your site url?
    * What sort of hosting are you on–shared? VPS? Dedicated?
    * What operating system is your site hosted on, i.e., Linux or Windows?

    also, could you perchance post your wp-config.php file, ***but please redact your user credentials!!!***

    I think that’s it for now. I hope you’ll reply so we can assist. Looking forward to hearing back from you.

    Thread Starter riverie

    (@riverie)

    Hi abletec,
    Thanks for looking at the issue, details below, however quick update, when grabbing the info to post, changed wp_debug to true, no errors showed, however issue then cleared, reset again to false and still no issue.
    Site url: https://goo.gl/7ACbnO
    Hosting: VPS (OVH), Linux, Ubuntu 14.04.4 LTS, Plesk 12.0.18

    WP Config (redacted)
    <?php
    /**
    * The base configuration for WordPress
    *
    * The wp-config.php creation script uses this file during the
    * installation. You don’t have to use the web site, you can
    * copy this file to “wp-config.php” and fill in the values.
    *
    * This file contains the following configurations:
    *
    * * MySQL settings
    * * Secret keys
    * * Database table prefix
    * * ABSPATH
    *
    * @link https://codex.www.ads-software.com/Editing_wp-config.php
    *
    * @package WordPress
    */

    // ** MySQL settings – You can get this info from your web host ** //
    /** The name of the database for WordPress */
    define(‘DB_NAME’, ‘******’);

    /** MySQL database username */
    define(‘DB_USER’, ‘******’);

    /** MySQL database password */
    define(‘DB_PASSWORD’, ‘*****’);

    /** MySQL hostname */
    define(‘DB_HOST’, ‘localhost:****’);

    /** Database Charset to use in creating database tables. */
    define(‘DB_CHARSET’, ‘utf8’);

    /** The Database Collate type. Don’t change this if in doubt. */
    define(‘DB_COLLATE’, ”);

    /**#@+
    * Authentication Unique Keys and Salts.
    *
    * Change these to different unique phrases!
    * You can generate these using the {@link https://api.www.ads-software.com/secret-key/1.1/salt/ www.ads-software.com secret-key service}
    * You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
    *
    * @since 2.6.0
    */
    define(‘AUTH_KEY’, ”);
    define(‘SECURE_AUTH_KEY’, ”);
    define(‘LOGGED_IN_KEY’, ”);
    define(‘NONCE_KEY’, ”);
    define(‘AUTH_SALT’, ”);
    define(‘SECURE_AUTH_SALT’, ”);
    define(‘LOGGED_IN_SALT’, ”);
    define(‘NONCE_SALT’, ”);
    /**#@-*/

    /**
    * WordPress Database Table prefix.
    *
    * You can have multiple installations in one database if you give each
    * a unique prefix. Only numbers, letters, and underscores please!
    */
    $table_prefix = ‘***;

    /**
    * For developers: WordPress debugging mode.
    *
    * Change this to true to enable the display of notices during development.
    * It is strongly recommended that plugin and theme developers use WP_DEBUG
    * in their development environments.
    *
    * For information on other constants that can be used for debugging,
    * visit the Codex.
    *
    * @link https://codex.www.ads-software.com/Debugging_in_WordPress
    */
    define(‘WP_DEBUG’, false);

    /* That’s all, stop editing! Happy blogging. */

    /** Absolute path to the WordPress directory. */
    if ( !defined(‘ABSPATH’) )
    define(‘ABSPATH’, dirname(__FILE__) . ‘/’);

    /** Sets up WordPress vars and included files. */
    require_once(ABSPATH . ‘wp-settings.php’);

    define( ‘WP_ALLOW_MULTISITE’, true );

    define (‘FS_METHOD’, ‘direct’);
    ?>

    htaccess (redacted)
    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /******/
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /*****/index.php [L]
    </IfModule>

    # END WordPress

    Hi, Ian. Well, this was helpful. Please get rid of the define multisite=true in your wp-config.php file. Please also confirm for us that the ownership/file permissions are as follows:
    * Your WordPress folder & all folders beneath it are owned by a user that belongs to the webserver group. I don’t know what your default is, though often it’s www-data. So if your WordPress user is wp, for example, add that user to the webserver group if that hasn’t already been done.

    I’m guessing this is being run on an Apache server, since you’ve got a .htaccess file, & the webserver group & user for Apache usually is www-data. Also, if you have caching enabled, you might wish to disable that for time being. Lastly, I don’t think SeLinux is set on in Ubuntu by default, but it can sometimes cause issues like that if it is–thanks @claytonjames for that tip.

    Looks like this may have resolved on its own w/o our help, but please try checking those things & let us know how you go. Lastly, if your problem is resolved to your satisfaction, please mark it so in order that the forum volunteers can understand your problem has been fixed & can therefore go on to help others. Thank you. & it’s been my pleasure making your acquaintance.

    Thread Starter riverie

    (@riverie)

    Hi abletec,
    Thanks for the response,yes running apache, files and permissions are fine, caching had not been enabled on the site as of yet. Thanks for the tip re Selinux, will mark as resolved as it appears to have rectified itself.
    Best wishes.
    Ian

    Thread Starter riverie

    (@riverie)

    UPDATE: Just for anyone who has a similar issue. On further investigation it was being caused by a chrome extension mobile browser extension. The extension itself is great and super for testing mobile views. However if you use when logged to a site in will cause the error previewing drafts issue.
    Hopefully information helps someone.

    I am receiving this error as well “Sorry, you are not allowed to preview drafts” – when it supposedly is published and I hit preview. AND when PUBLISH is initialized, the change(s) do not propagate to the live site either. I did not create this site, but have been assigned Administrator role. I have verified capabilities of this role, disabled plugins and tested, had another Administrator test his profile to see if WordPress would publish changes, but no luck. Examined wp-config.php file, which is not extensive… but nothing really shows a ‘smoking gun’ that I can see. I’m not fluent with WordPress by any means. I’m a Network Engineer that gets pulled into website projects on occasion. Any input would be much appreciated.

    Sorry, you are not allowed to customize this site.

    I am receiving this error.
    Sorry, you are not allowed to customize this site.
    please help me out.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘WordPress Error, Sorry, you are not allowed to preview drafts.’ is closed to new replies.