sweettea2

Thanks for the assistance!

It says about Post Expirator that “The plugin hooks into the wp cron processes and runs every minute by default, but can be configured to use any cron schedule (hourly, twicedaily, daily, etc).”

It seems like there is some trouble with getting custom post types to work with the expirator plugin, so I wonder if that’s related to why they don’t auto-expire with User Submitted Posts?

This plugin (https://www.ads-software.com/plugins/electric-studio-auto-expire-post/) does seem to work, but hasn’t been updated in 3 yrs. I wonder why it works and not the Post Expirator?

Thanks!

Two of the sites that had this issue for me were on servers using PHP 5.3xx, which definitely seems to be related to the problem.

Ditto. I noticed the issue on two sites I webmaster too. Disabling W3TC or disabling the Page Cache or gzip compression in the Browser Cache settings as mentioned above seemed to help. I really hope this can be fixed!

Also, weird thing is that Chrome/GTMetrix and https://www.gidnetwork.com/tools/gzip-test.php say the home page of one of the sites is gzipped even with the gzip compression setting unchecked in W3TC.

• This reply was modified 8 years, 2 months ago by sweettea2.

Ditto. I am seeing the error below on one of my client’s sites…

‘PHP Warning: mysql_num_fields() expects parameter 1 to be resource, boolean given in /XXXX/XXXXXX/public_html/wp-includes/wp-db.php on line 3026’

Scratch that…I thought I got it working, but then tried logging into the admin area of the WP site and got a 404 error. So, it works on the front-end, but messes up the admin area and won’t let me see the dashboard if I go to example.com/blog/wp-admin. It takes me to the login page if I go to example.com/blog/wp-login.php directly, but if I log in, it goes to a 404.

Thoughts…??

I got it to work!!!!! This link and this link got me on the right track and so the final web.config code that works is below for reference. I really appreciate your patience and assistance. All the best!

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <system.webServer>

	<defaultDocument enabled="false" />
	<rewrite>
      <rules><rule name="Main Rule" stopProcessing="true"><match url=".*"/><conditions logicalGrouping="MatchAll"><add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true"/><add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true"/></conditions><action type="Rewrite" url="index.php"/></rule>

			<rule name="No slash root" enabled="true" stopProcessing="true">
            <match url="^$" />
            <action type="Rewrite" url="index.php" />
        </rule>
			</rules>
    </rewrite>
  </system.webServer>
</configuration>

Link to Screenshot

Above is a link to a screenshot of the Permalinks page. Also, the plugins I have active on the site are:

• Attachment Pages Redirect
• Disable Comments
• Easy Author Image
• Easy Updates Manager
• Google XML Sitemaps
• Quick Page/Post Redirect Plugin
• Sucuri
• Wordfence
• WP Sitemap Page
• Yoast SEO

Thanks again for all your assistance!!

Ok. No, the site in the root location is a custom php site (non-WP).

Unfortunately, that didn’t seem to fix the issue. I still wonder if something in the main site’s web.config is causing this? I’ve posted a snippet from the main web.config below (didn’t post the whole file for security reasons). Thanks again for your assistance!!

<system.webServer>?
??? <rewrite>
??? <rules>
??????? <rule name="Redirect domain.com to www" patternSyntax="Wildcard" stopProcessing="true">
??????????? <match url="*" />
??????????? <conditions>
??????????????? <add input="{HTTP_HOST}" pattern="example.com" />
??????????? </conditions>
??????????? <action type="Redirect" url="https://www.example.com/{R:0}" />
? </rule>
</rules>
</rewrite>
</system.webServer>

Sure! Below is the code that’s in the /blog/ subfolder with the WordPress files. Do you need the code from the main folder web.config as well?

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <system.webServer>
   <rewrite>
    <rules>
        <rule name="Main Rule" stopProcessing="true">
            <match url=".*" />
            <conditions logicalGrouping="MatchAll">
                <add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
                <add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
            </conditions>
            <action type="Rewrite" url="index.php" />
        </rule>
    </rules>
</rewrite>
  </system.webServer>
</configuration>

Ok, I think it’s working on the site I saw the issue on. When I moved the site from a subfolder to the main folder, the Sucuri plugin didn’t fully move over. I switched to All in One SEO Pack and thought I was going to have to stick with that, but after fully removing Sucuri and readding / reactivating everything (including Sucuri / Wordfence), it’s not showing the message anymore. I love this Yoast plugin, but this was a hassle…hope everything’s resolved now. Thanks!

I am getting the “Your homepage cannot be indexed by search engines.” message too and deactivating Sucuri and Wordfence on the site didn’t help…please help Yoast!

Got it working! I’m using Interface (free WP theme) and it was a conflict with the add-image-script-widget.js and add-image-script.js files in the theme. I just did a search in the theme for “send_to_editor” and both those files came up. Removed those files and all references to them and it’s working! Thanks for the help.

I don’t know…sorry. Here’s the plugins I currently have activated:

amr shortcode any widget
Attachment Pages Redirect
Contact Form 7
Contact Form DB
Disable Comments
Display Widgets
Quick Page/Post Redirect Plugin
Remove WP version and shortlink
SSH SFTP Updater Support
WordPress SEO
ZigWidgetClass