Anthony Laurence

Well…. you could try. ?? But your best bet would be to reach out to a dev for this one, since you would have to save the initial log in to the database. That can get a little hairy (and break things very easily) if your not used to something like that.

Sorry mate.

Your welcome. Good luck!

I don’t know of any existing plugins that are out there, but it wouldn’t be to difficult to create.

Essentially you would grab the users initial log in timestamp and break it down into a day. Then at each subsequent log in you compare the initial timestamp to the current timestamp and then after 5 days, you include the additional content.

404 means that the files that the browser looks for on the server to “build” the website can’t be found. There can be many different reasons that you get a 404 error.

Your best and quickest road to resolution would be to contact your hosting company about this.

Deactivate all your plugins and then try to update a page. if it works you then found you’re culprit. Activate each plugin, and then make an update to a page. Keep going until the admin breaks on the update; that’s your faulty plugin.

if you deactivate all your plugins and you’re still getting an error without reactivating any, contact GoDaddy. They should be able to find and correct any issues; that’s what you pay them for.

You could try that, but it sounds more like a server/CDN caching issue. As Tara suggested, clear your server cache via your host and clear any CDN if you are using it.

Then clear your browser cache and see if that fixes anything.

To be honest, if the site was just created and you’ve only just submitted it to the SEs, they barely had a chance to crawl and index your site, so you will end up with some wonky results until they properly categorize you.

Also, another thing to be careful of is that as you repeated search for and click your domain, Google remembers that and will push your site higher in the rankings for you, not necessarily for anyone else.

Increased rankings is a slow process even with a rock solid strategy.

No worries! But now that I think about this, shouldn’t we doing this in a child theme…?

Thelaakgroup, once you’ve made the changes, just keep in mind that if you ever update the theme, your changes will be erased since you’re hacking the core files. Updating the theme will update the core files and will overwrite everything you did.

Hmmm…… Then your theme might be using a blog.php file. If so, go into that file and find all of the references to

<img src="<?php echo $feat_image[0]; ?>" alt="<?php the_title(); ?>" title="<?php the_title(); ?>" />

and replace it with

<a href="<?php the_permalink(); ?>">
     <img src="<?php echo $feat_image[0]; ?>" alt="<?php the_title(); ?>" title="<?php the_title(); ?>" />
</a>

Thanks NeoTechnomad! Oddly enough wrapping the dirFunc() in the admin test was still throwing the error, but if I wrapped the re_once($dir.’directoryTemplate.php’) in the admin test it works fine.

Also, thanks for the tip on the pluggable functions; I had not come across that yet.

That should do it.

In addition to turning off any caching plugins, if you are caching on the server, or through a service like Cloudflare, you’ll need to clear those as well.

Hi Thelaakgroup,

That is correct, you should be able to take what katrna put in the Pastebin and replace what is in the index.php via your editor in the Dashboard.

Click save and everything should work fine.

The bit of code your looking to replace starts on line 38 in the Pastebin.

FYI, here is the htaccess for the old site:

Options +FollowSymlinks
RewriteEngine on
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule !^index\.php$ index.php [NC]
ErrorDocument 404 /_repot/error/404.html
ErrorDocument 500 /_repot/error/500.html
ErrorDocument 503 /_repot/error/503.html
# BEGIN W3TC Browser Cache
<IfModule mod_deflate.c>
    <IfModule mod_headers.c>
        Header append Vary User-Agent env=!dont-vary
    </IfModule>
        AddOutputFilterByType DEFLATE text/css text/x-component application/x-javascript application/javascript text/javascript text/x-js text/html text/richtext image/svg+xml text/plain text/xsd text/xsl text/xml image/x-icon application/json
    <IfModule mod_mime.c>
        # DEFLATE by extension
        AddOutputFilter DEFLATE js css htm html xml
    </IfModule>
</IfModule>
# END W3TC Browser Cache
# 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

Not sure if this helps. htaccess calls aren’t my strong suite….

There is an htaccess in the Beta folder.

# 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

After that is code for GZipping and settings for the caching plugin, which shouldn’t affect this.

We are using Apache on a shared server through Siteground.

Thanks. I tried the code above but no changes. I already have the WP_HOME and WP_SITE urls set for the Beta folder. I tried the rest of the code but nothing.

I checked and the links aren’t an issue. Most of the menu links are generated by WP, and the paths look right.

It’s funny, because when you click on About Us, for example, the URL it uses is pacharters.org/_BETA/about-us, as it is supposed to, but it uses the old theme. But it doesn’t pull in any content because I’m using a new database.

I’ve used Beta folders in the past and this is the first time I have had this issue….

I know the developer for the old site had some “creative” ways that he coded their site. Do you think it might be a configuration that he used? Maybe an htaccess directive?