wordpress .htaccess & .htpasswd issue - wordpress

I have a strange issue here. My client site is suspended due to spam messages by one.com. After deleting the comments, the technical support guy told me to generate .htaccess and .htpasswd file by using one.com's support page and upload it into root. Deleted old files and uploaded the new files a per the supporting guy. But site shown an internal error, then the technical guy said 'delete' both files and try. Then the home page is loading but inner pages showing 404 error.
Anyone here have a solution for this? this is the site http://www.jayabhattacharjirose.com/
Thanks in Advance

This is a problem with permalinks. Try the one of the following three solutions.
1: Set your Permalinks back to default, if things start working as expected then try re-setting Permalinks back to what you want.
2: Try going in your Dashboard to Settings > Permalinks. You don't need to change anything on the Permalinks page, but just click Save Changes at the bottom. Then check your site to see if that fixed it.
3: Try changing options on the Permalinks page if you want to change the way the URL looks from p=### to the /date/page format or others.

Reset your permalink to default and then again set it your required permalink structure so that WordPress creates a new required .htaccess file for it.
And if you have backup of your project then try to use the old .htaccess file.

Related

WordPress Permalinks Issue

So we installed a fresh version of WP. Thanks for the help earlier.
The last issue we cannot figure out is why we cannot navigate the site.
Basically, when we try to navigate internally into the website we imported into the sandbox, it gives the following:
The requested URL /page-name/ was not found on this server.
If it's the ugly / default Permalink, we can view the files under pages, but we cannot navigate even. The pages were set to /page-name/, which I'm pretty sure is /%postname%/. I've scoured online. I've put up a blank .htaccess file, changed the permissions to 666 for writing purposes.
What I've tried included:
Replacing the .htaccess with a blank (I renamed the old one to be a backup) - it generates information to the file.
We can view pages manually that way, but we cannot navigate through the "live" site with it running this way.
Is there a second source I should be referring to for updates on the .htaccess file? Is there tricks online I may have overlooked? Any input would be appreciated!
Thank you!
Thank you Milap for the comment above! It turned out to be the AllowOverride being false. Apparently this have to be enabled in order for it to work. To those who plan to make this change, restarting your server is required.
Please refer to section AllowOverride Not Enabled section of their documentation: https://codex.wordpress.org/Using_Permalinks

One page won't show on wordpress after moving from live to localhost

I moved my website from live to localhost to make some modifications to it and I have encountered a problem, one page will not show up: "Oops! That page can’t be found.".
I have tried the following
1. activated rewrite_module
2. deactivated each plugin to see if anyone is causing the problem
3. recopied the database and files in case of failure during the first transfer
4. read that resetting permalinks might solve the problem. Changed permalinks to default - the page now works, but when I changed back to custom the problem is still there.
This is weird because only one page does not seem to show, every other page works fine and also there is no problem on the live version.
I ran out of solutions can any one please help?
This may be caused by the permalink or .htaccess
check the url of your page if no issues on URL then
Follow this steps once:
Go to settings-> permalink-> set it as default ->Reload or refresh
Then again now Go to settings-> permalink->postname
Your .htaccess will get update with the permalink.
This could be a problem with htaccess. When using the query string urls in wordpress, no htaccess is required, but for anything else Wordpress uses mod_rewrite.
Is htaccess turned on your localhost Apache server? In httpd.conf, AllowOverride All should be turned on in your active directory.
Is Wordpress able to create new files? Insufficient permissions might prevent it from creating the htaccess file.
Finally, check that your links are pointing to the right place. Sometimes the problem is as simple as a misspelling in your link ;) Good luck.

simple press permalink 404 error

I'm trying to use the Simple:Press forum plugin for WordPress. If i go into my sites Settings/Permalinks and select anything other than Default, I get a 404 error whenever I try to access any of the forums or user profile.
Does anyone have a workaround for this?
Edit: I should add this is on a Windows machine and I have added the Web.config file which seems to work fine for other pages
Is the proper .htaccess file being created when permalinks are enabled? Could be a directory not writable issue.
Depending on which version of Wordpress you have, this might be the fix. It's a mod rewrite error.
Right click on the Bookmarklet, and change
u=’+e(l.href)+’
to
u=’+e(l.href.replace(///g,’\/’))+’
A quick work around is to delete part of the URL in the pop. Delete after
http%3A%2F%2F
after the u=, up through the beginning of the domain for the website.

Wordpress template pages not being displayed in 3.2 :|

Few months ago, I developed two template pages on wordpress 3.1 and they were working fine. Now, I installed latest wordpress software. I created a new page with the same name and selected the template. But the link is showing a "404 Not Found" error.
My site URL goes like this: http://localhost/myBlog/about
where "about page" has to use a template. The same permalink is shown when creating the page but viewing page is showing 404 error. It's weird. May be some permalink issue?
Well assuming this is a new installation and not an upgrade, I am guessing that your permalink structure is messed up. There are a couple ways to fix this. In general, Wordpress tries to modify your .htaccess file itself.
Go to your old installation and look under Settings -> Permalinks. If it is different from your new install, then change them to be the same and save. If they are the same, then change it to something else and then change it back. This should force Wordpress to resave the settings to your .htaccess file. If it can't write to the file it should tell you.
Alternatively you could look at the .htaccess file of your old installation and copy the values there over to your new installation. Although I think letting WP do it for you is probably the safer route.
If you can access your database, You need to go to the wp-options table and change the url there. The other options there. Were you working on a local server?

WordPress with Yahoo! Hosting... Almost there

EDIT:
Yeah, so this problem is really unsolvable. Yahoo prevents access to .htaccess, even from WordPress itself trying to change it. I had to settle for writing a script on the default homepage that redirects browsers to "www.abc.com/index.php" if they go straight to "www.abc.com". You always have to deal with "index.php" being in the address bar but it's better than not having permalinks...
/EDIT
Yahoo! Small Business hosting seems specifically engineered to make WordPress difficult-- but it's my client's host and there's not much I can do about it. I'm trying to move WordPress into the root directory, and I'm sooo close to having it done.
I've read and read and read about how to get the Permalinks to work right, and since Yahoo! hosting doesn't let you modify htaccess I am pretty much up s*** creek. I'm using the simple permalink structure of "/%postname%/", which once I moved to the root, stopped working. I have changed it to "/index.php/%postname%/", which allows you to see the pages if you manually type in index.php before the page name or if you are logged into the admin area and "View Page". Also, the correct permalink shows on all of the pages in the editor.
However, WordPress doesn't let you change the permalink of the static page you use as the front page.
Long story short, if I go to "www.abc.com/index.php", the links in the menu all work fine. However, if I just got to "www.abc.com", the links don't pick up the "index.php" from the permalink structure. I need to fix this, so if anyone knows how to either:
Change the permalink of the static front page
Fix something in the database if I install PhpMyAdmin
Work around not having access to .htaccess
Put a small script somewhere on the index page to append "index.php" to the url
Any other suggestions
It seems it would work if I was NOT using a static front page but rather the blog, but this isn't an option. I've tried changing the "Tag base" setting to no avail, as well as deactivating the Yahoo! Custom Permalinks plugin (and reactivating it again after that failed...). Could really use some help!
Check out Giving Wordpress its own directory. I can see how this could solve your problem. Also make sure that you have done the obvious, and change your url for WordPress address (URL) Site address (URL) inside the general settings page. Perhaps the static homepage should be developed outside of wordpress, and then you can follow the steps provided in the link I provided. Hope this solves your issue.
Yahoo doesn't allow users access to the htaccess file which means that you can't the mod_rewrite rules needed for custom permlinks. The Only way around it that i've heard it works (never tried it myself) is to add /index.php/ to the beginning of your custom structure so: Go to Permalink Settings > Select Custom Structure. And set the value as /index.php/%postname%/ or what ever you want as long as you add /index.php/ before it.
Hope this helps.
I had a similar problem with this host (in 2018! 4 years after your question) that I finally solved by changing the permalink settings.
Settings > Permalink Settings > Custom Structure: /index.php/%postname%/
I wish there was a better solution but Yahoo Small Business still doesn't allow .htaccess files - after several frustrating rounds with customer service, I finally admitted defeat and used this work around.

Resources