404 Error

The manual file editing was probably unnecessary, and may actually be causing some odd issues at this point. With WampServer, the only thing required to enable mod_rewrite is usually just clicking on the WampServer system tray icon > Apache > Apache Modules > scroll down to and select “rewrite_module” and the server will do a graceful restart on its own. After that mod_rewrite should be functioning.

A quick before and after visual check:

1) Before enabling the rewrite_module from the wamp icon menu in the system tray, open phpinfo() from the Tools menu in the WampServer project page and scroll down to “apache2handler”. mod_rewrite will/should not appear in the Loaded modules list.

2) Enable the rewrite_module as I described above, and revisit phpinfo(). This time, mod_rewrite should show up in the loaded modules section.

That should be all that’s required. No manual file editing needed.

I’m really grateful for these detailed instructions you’re giving me!

I restored all settings of the httpd.conf file back to their original settings. I stopped all services, unchecked the mod_rewrite module, and looked at the php.info file as instructed. As you had predicted, the mod_rewrite module was not present.

Image: https://cloudup.com/cFs4WFOLie4

I went to the modules, enabled the rewrite_module, and revisited phpinfo(), as instructed. As you had accurately predicted, mod_rewrite now shows up in the phpinfo() section.

Image: https://cloudup.com/c2ryB-T4f9X

I still seem to be having the same problem, however.

When I click on a custom post type, I still get the same response with link structure, and all the content and images are displayed. I still get 404 errors with common pages, however.

I’ll be back. I just remembered, I also have a “default” 4.2.2 scratch site that doesn’t have custom post types on it I should check too, with the new settings. Perhaps the comparison of the two sites could offer some insights.

Again, thank you so much.

Some promised follow-up.

I think the problem may be related to the child theme we have, or possibly the settings we have for our Types plugin.

The “default” WordPress 4.2.2 using a TwentyFifteen theme runs fine, as does a “default” WordPress 4.2.2 using the TwentyFifteen theme with the Types plugin on it. The problem seems to come in with this customized child theme that we created, and possibly to the way I imported data for it. I hadn’t realized at first that when I was testing the custom post types, I assumed everything was fine because I saw all the images associated with data I thought I had imported. A closer look showed that the images were actually pointing to the old site, not imported content as I had thought–and the custom post types weren’t actually working as well as I first thought. Please accept my apologies for not checking this more thoroughly before coming here.

Still, there seems to be a problem associated with Permalinks on the 4.1.1 site with the child theme. On the other two sites, the basic 4.2.2 and the basic 4.2.2 with a TYPES plugin custom post type, the Permalink Settings is “Custom Structure”. When I try to set the Permalink Setting to the same in the local site with the child theme, it won’t allow me to “Save” the structure like that, and instead defaults to the “Post Name” option after each attempt to save the Permalinks.

Image: Basic WordPress 4.2.2, no plugins, works with default settings
https://cloudup.com/cTpsCDelv75

Image: Basic WordPress 4.2.2 with Types Plugin Permalinks https://cloudup.com/c1e0oxqRTd4

Image: Scratch Site WordPress 4.1.1 with child theme does not allow Permalinks to be saved as Custom Structure, but defaults to Post Name when saved. https://cloudup.com/cQyFBfOgDth

Bottom line, I don’t think the problem has with anything to do with Apache, or the set up on localhost, I now think it’s a theme or TYPES plugin settings problem on my part.

At any rate, thank you so so much for the feedback–it allowed me to clean up the httpd.conf file in Apache and simply check the rewrite_module. So simple, and so easy, and I really appreciate the input of the phpinfo() page.

I personally think this topic should be considered “resolved”, since the default sites are working fine, but please feel free to re-open if you think it should remain open! Again, thank you for the help! I really appreciated it!

I’m glad it helped a bit. I hope you get to the bottom of the issue with the plugin. Good luck to you!

I promise you, it helped more than a “bit”! Thank you again! ??