Forum Replies Created

Viewing 15 replies - 226 through 240 (of 301 total)
  • One more thing to consider with google is that you MUST use port 587 and tls for relay due to the imminent deprecation of ssl and rc4 on their smtp servers.

    If you want, there are simple php files you can use to test your mail independent of any plugins. They can connect to your relay server and output errors to screen for you to troubleshoot.

    Thread Starter 7thcircle

    (@7thcircle)

    I do not understand the idea of using an extra plugin to fix a security flaw. I also do not understand the need to compromise security for debugging purposes. You debug on a test site and fully secure a production site as best practice. By your comments, am I to believe that this plugin is still in beta?

    Thread Starter 7thcircle

    (@7thcircle)

    I have 4 options under twitter

    1 drop down for default twitter card – set to summary
    2 twitter site – set to @7thcircledesign
    3 check box for show twitter author – checked
    4 twitter domain – set to 7thcircledesigns.com

    I have not entered the twitter url anywhere except in the social profile links box, and I have also tried removing it from there to no avail.

    I am not caching this site, I have tried multiple browsers and computers, and I am not running any other plugins that would add this information.

    When I run the test scan no duplicate information is found.

    Thread Starter 7thcircle

    (@7thcircle)

    <meta name=”twitter:card” content=”summary” />
    <meta name=”twitter:site” content=”@7thcircledesign” />
    <meta name=”twitter:creator” content=”@https://twitter.com/7thcircledesign” />
    <meta name=”twitter:domain” content=”7thCircleDesigns.com” />

    No issues for me across dozens of sites and hosts. What I can say is regardless of the documentation, there are several items that will cause the majority of your issues, and these are in no particular order.

    1. misconfigured plugin for your host
    2. your host being on a black list
    3. your host blocking mail on some ports
    3. your sending address (gmail as opposed to your domain)
    4. your site being at a subdomain (WP uses wordpress@siteaddress to send, so wordpress@subdomain.domain.tld)
    5. your sending address not being an actually address on your mail server

    For me, I like to use google apps for my email, and I configure the relay to accept mail from my website. I then use my own plugin that is similar to wp-smtp-mail to send all of my mail through google. On my sites that use a subdomain, my plugin allows me to set a sender address. I also make sure that my sending address is a valid address, so I have created a wordpress@domain.tld address for sites that need that.

    Your mileage may vary, and you may run into an issue with the plugin, but for me this works well and solves ALL mail issues regardless of the plugin or feature of WP I am using.

    Look into wp-smtp mail and use a real mailserver instead of the one your host provides.

    Please post what the issue was so that others can know and the developer can implement a fix if necessary.

    The biggest issues I have seen are that your hosts mail servers are blacklisted, or you are sending from a domain that does not match your website.

    The biggest offenders on receiving are gmail, yahoo, aol, microsoft, etc

    Thread Starter 7thcircle

    (@7thcircle)

    The issue does not exist on my dev server, it is only on this install

    Thread Starter 7thcircle

    (@7thcircle)

    I have emailed the files

    Thread Starter 7thcircle

    (@7thcircle)

    Yeah, it has me stumped. Since the same combo works on the dev site and not prod I was hoping someone had seen something that I could beat with a stick and make it work. I hate to have access to the editor available since it makes it easier to break things if the end user is not careful.

    Thread Starter 7thcircle

    (@7thcircle)

    I saw a few minor issues in the logs and sent them to the plugin devs, but nothing that would explain the issues I had been seeing.

    I am now at 30 hours with no 500 errors after several changes.

    1. Better search replace and update all internal redirects (many items were doing http to https redirects), this lowered the number of errors

    2. Disable cron and make it a server job, lowered to a handful of errors once a day

    3. Changed cache preload to weekly from daily

    4. wp-config tuning and some selective bot blocking in htaccess

    Mailchimp gives me a few options. Did you authenticate your domain? Do you get the subscription?

    I have seen a post not get sent due to the timestamp on the post being before today’s scheduled check and not actually being published until after today’s scheduled time. I have also seen it where the feed is not updated correctly due to caching issues on your site. Most cache plugins are supposed to regenerate anything that changes or anything that is new, but sometimes they don’t, so a manual cache purge can fix it too.

    Check your feed after posting to make sure it shows to verify the cache.

    Thread Starter 7thcircle

    (@7thcircle)

    <?php

    /***************************************
    PRODUCTION SERVER. OPTIMIZED FOR SPEED.
    ****************************************/
    define(‘WPCACHEHOME’, ‘/home2/XXXXXXXX/public_html/wp-content/plugins/wp-super-cache/’ ); //Added by WP-Cache Manager
    define(‘WP_CACHE’, true);
    define(‘WP_DEBUG’, false);
    define(‘SAVEQUERIES’, false);
    define(‘SCRIPT_DEBUG’, false);
    define(‘COMPRESS_CSS’, true );
    define(‘COMPRESS_SCRIPTS’, true );
    define(‘CONCATENATE_SCRIPTS’, true );
    // log errors in a file (wp-content/debug.log), don’t show them to end-users.
    define(‘WP_DEBUG_LOG’, true);
    define(‘WP_DEBUG_DISPLAY’, false);
    define(‘ENFORCE_GZIP’, true);
    // DATABASE
    define(‘DB_NAME’, ‘DB_NAME’);
    define(‘DB_USER’, ‘DB_USER’);
    define(‘DB_PASSWORD’, ‘DB_PASSWORD’);
    define(‘DB_HOST’, ‘localhost’);

    // DOMAIN & URL
    define(‘PROTOCOL’, ‘https://&#8217;);
    define(‘DOMAIN_NAME’, ‘www.artstopinc.com’);
    define(‘WP_SITEURL’, PROTOCOL . DOMAIN_NAME);
    define(‘PATH_TO_WP’, ‘/’); // if your WordPress is in a subdirectory.
    define(‘WP_HOME’, WP_SITEURL . PATH_TO_WP); // root of your WordPress install
    // Using subdomains to serve static content (CDN) ?
    // To prevent WordPress cookies from being sent with each request to static content on your subdomain, set the cookie domain to your non-static domain only.
    // define(‘COOKIE_DOMAIN’, DOMAIN_NAME);

    /**#@+
    * Authentication Unique Keys and Salts.
    *
    * Change these to different unique phrases!
    * You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org 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’, ‘ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ’);
    define(‘SECURE_AUTH_KEY’, ‘ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ’);
    define(‘LOGGED_IN_KEY’, ‘ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ’);
    define(‘NONCE_KEY’, ‘ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ’);
    define(‘AUTH_SALT’, ‘ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ’);
    define(‘SECURE_AUTH_SALT’, ‘ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ’);
    define(‘LOGGED_IN_SALT’, ‘ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ’);
    define(‘NONCE_SALT’, ‘ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ’);

    /* ———————— SETTINGS COMMON TO ALL SERVERS ——————— */
    define(‘TABLE_PREFIX’, ‘wp_’); // Something else than the default wp_. Only numbers, letters, and underscores.
    define(‘WP_POST_REVISIONS’, 3 ); // How many revisions to keep at max.
    define(‘AUTOSAVE_INTERVAL’, 180); // in seconds
    define(‘EMPTY_TRASH_DAYS’, 3); // in days (use 0 to disable trash)
    define(‘IMAGE_EDIT_OVERWRITE’, true); // Allows overwriting images when editing them.
    define(‘MEDIA_TRASH ‘, true);

    // WORDPRESS’ LANGUAGE _ Default is ‘en_EN’
    define(‘WPLANG’, ”);

    // DB INTERNALS
    define(‘DB_CHARSET’, ‘utf8mb4’);
    define(‘DB_COLLATE’, ”);

    // Database repair page
    //define(‘WP_ALLOW_REPAIR’, true); // wp-admin/maint/repair.php

    // DIRECTORY CUSTOMIZATION
    // make it less obvious that your site is using wordpress.

    // rename wp-content folder
    // define( ‘WP_CONTENT_DIR’, dirname(__FILE__) . ‘/wp-content’ );
    // define( ‘WP_CONTENT_URL’, WP_SITEURL.’/wp-content’);

    // rename uploads folder
    // define( ‘UPLOADS’, ‘/wp-content/uploads’ );

    // rename plugins folder
    // define( ‘WP_PLUGIN_DIR’, dirname(__FILE__) . ‘/wp-content/plugins’ );
    // define( ‘WP_PLUGIN_URL’, WP_SITEURL.’/wp-content/plugins’);

    // You cannot move the Themes folder, but your can register an additional theme directory
    // register_theme_directory( dirname( __FILE__ ) . ‘/themes-dev’ );

    // Prevent users from editing themes and plugins via the UI
    define(‘DISALLOW_FILE_EDIT’, true); // Disable the Plugin and Theme Editor
    define(‘DISALLOW_FILE_MODS’, false); // Disable WordPress Plugin and Theme Installation, Update and Delete

    // Cron system
    define( ‘DISABLE_WP_CRON’, true ); // If you can, disable wp_cron: use a real cronjob to trigger /wp-cron.php
    //define( ‘WP_CRON_LOCK_TIMEOUT’, 120 ); // cron repeat interval
    //define( ‘ALTERNATE_WP_CRON’, false ); // Issues with cron? Try this setting as a last resort.

    // SSL
    if (PROTOCOL === ‘https://&#8217;){
    define( ‘FORCE_SSL_LOGIN’, true );
    define( ‘FORCE_SSL_ADMIN’, true );
    }

    // If you don’t plan to post via email, decrease this
    define(‘WP_MAIL_INTERVAL’, 604800); // 1 day (instead of 5 minutes)

    // MEMORY ALLOCATION
    define(‘WP_MEMORY_LIMIT’, ’64M’);
    define(‘WP_MAX_MEMORY_LIMIT’, ‘256M’); // Admin area specifically

    // Auto-updates
    define(‘CORE_UPGRADE_SKIP_NEW_BUNDLED’, true); // Make WordPress core updates ONLY update the core without Akismet & Hello Dolly
    define( ‘WP_AUTO_UPDATE_CORE’, false ); // Disable all core updates

    /* ———————— OTHER CONSTANTS YOU COULD NEED ——————— */

    // MEMORY ALLOCATION
    //define(‘WP_DEFAULT_THEME’, ‘twentyeleven’); // Custom Default Theme

    // Custom Database Table for Users
    //define( ‘CUSTOM_USER_TABLE’, $table_prefix.’peeps’ );
    //define( ‘CUSTOM_USER_META_TABLE’, $table_prefix.’peepmeta’ );

    // Auto-updates
    //define( ‘AUTOMATIC_UPDATER_DISABLED’, true ); // Disable all automatic updates
    //define( ‘WP_AUTO_UPDATE_CORE’, true ); // Enable all core updates, including minor and major
    //define( ‘WP_AUTO_UPDATE_CORE’, ‘minor’ ); // Enable core updates for minor releases (default)
    //define( ‘DO_NOT_UPGRADE_GLOBAL_TABLES’, true ); // Disable DB Tables auto-update

    /* ————————– STOP EDITING PAST THIS POINT ——————— */
    $table_prefix = TABLE_PREFIX;

    if(WP_DEBUG_LOG){
    @ini_set(‘log_errors’,’On’);
    }
    if(WP_DEBUG_DISPLAY){
    @ini_set(‘display_errors’,’On’);
    }
    // Adapt your servers to the chosen locale.
    setlocale(LC_ALL, WPLANG);

    // For compatibility with old plugins
    define( ‘PLUGINDIR’, WP_PLUGIN_DIR );

    /** Absolute path to WordPress. */
    if ( !defined(‘ABSPATH’) )
    define(‘ABSPATH’, dirname(__FILE__) . PATH_TO_WP);
    require_once(ABSPATH . ‘wp-settings.php’);

    Thread Starter 7thcircle

    (@7thcircle)

    I have tried twenty twelve with all plugins disabled, I have tried my theme with all plugins disabled, and I have reinstalled 4.5.2

    I have a duplicate site on a different server with the same hosting company, same plugins and config, same theme, everything works as expected. Could it be in the db? What about in the server config? Maybe in my php.ini (both sites are @ 5.6)

    I have tried a clean htaccess file too.

    error reporting is on in php.ini and I have enabled the debug log but nothing is showing in the logs

Viewing 15 replies - 226 through 240 (of 301 total)