Nick
Forum Replies Created
-
In case it isn’t clear in my original post,
example.com/site2is just a WordPress page. It and it’s subpages are intended to be a second site, with a unique domain.Forum: Themes and Templates
In reply to: Get Current Post Tags (Without Link to Tag Page)Going Up,
Thanks for your solution! This worked perfectly for me.
sellerscentral, deepbevel,
esmi’s link has more info for a complete understanding but the loop is the area of your code that looks for posts and then performs the same action on the ones that it finds (usually spitting out the title and content of the post into the code).
Forum: Fixing WordPress
In reply to: Theme changes don’t apply until I upload a new themeA week after the day I first noticed this issue, it no longer seems to be occurring. It is possible that the issue will return as easily as it disappeared. I’m reluctant to call this topic “resolved” because I did not discover the source of the issue.
I’ll be back if I have more info 🙂
Forum: Fixing WordPress
In reply to: Theme changes don’t apply until I upload a new themeesmi,
I made changes to footer.php and waited over an hour and the changes did not display on the site.
I tried deleting footer.php on the remote server, then making a change to it locally, then uploading the new footer.php. The result was that while the file was absent, on the site it was absent. After I uploaded the changed footer.php, it displayed the footer unchanged. I don’t know anything about hosting caching but the files are definitely being remembered somewhere.
Thing is, if I change my CSS files within the theme, or an HTML page somewhere else on the server, those changes are reflected immediately. It is only my WordPress stuff that behaves this way.
Could it still be an issue with my hosting setup or did that just get rule out?
Forum: Fixing WordPress
In reply to: Pretty Links works but 403 on new pagesSolution Found. This turned out to be something unforgivably simple!
If you are experiencing an issue where some of your WordPress pages are “403 Forbidden” check your site. If you already have files or folders in the same directory as your WordPress install by the same name as the page you are trying to see, you might be a redneck.
No but seriously, WordPress is not able to resolve at a page located at
example.com/team/if you have a “team” directory there already!Delete or rename the file or folder and you should be ready to go.
Forum: Fixing WordPress
In reply to: Pretty Links works but 403 on new pagesUpdate
It seems that none of the settings that I have discussed thus far are causing this issue. I am now able to add pages and land on them at the expected, “pretty” URL structure.
The two pages that were not working are still resolving as “403 Forbidden”. If I delete them and recreate with the same name, there is no change. But if I rename them, I am able to resolve at the new expected, “pretty”, URL structure.
I am new to databases. Does this indicate corrupted entries that I need to erase in order to create pages with those desired slugs again?
Forum: Fixing WordPress
In reply to: Pretty Links works but 403 on new pagesI disabled the only active plugin, Disable Canonical URL Redirection and it does not seem to make a difference.
From Dashboard > Permalinks, my custom structure is
/%category%/%postname%/. But WordPress is telling me that my .htaccess is not writable. It is set to 766, but I had to paste in the rewrite code manually.When I go to look at my pages from Dashboard > Pages, I see that my permalinks for each of my pages are structured like this:
/index.php/services/instead of the expected structure. The only part of the slug that I can edit isservices.And still, the issue persists: some pages resolve at the custom structure while others 403 Forbidden. Comments appreciated.
Forum: Fixing WordPress
In reply to: Redirect LoopOkay, for anyone who has a similar setup, here’s a fix, one second after I posted the issue.
- In your WordPress admin account look at your General Settings. My “Blog address (URL)” setting was the default “example.com”. So whenever I would land on my WordPress index.php, it was actually set to redirect back to the directory resulting in a redirect loop.
- Change “Blog address (URL)” to “example.com/index.php”
- Install the Disable Canonical URL Redirection plugin. (See Managing WordPress Plugins if you don’t know how.)
You should now see that when you go to your site ends up at the correct location instead of getting caught up in a loop.