I just checked Integration>Storage Locations.
Everything shows Location found, Write-denied.
Would this be a problem, I presume?
Back to square one.
The new wpadmin account is deleted. All owner/group info is as it was when the 404 first manifested. Permalink structure is, for the moment, set back to its original “Month and name” format.
I verified that Integration>Storage Locations now shows Location found, Write-OK for all locations.
I installed the WP-DBManager plugin and ran a backup and optimize. Results were the same as when I used phpMyAdmin to do this: no apparent change, the 404 persists.
Here is a forum request without any 302 error, just the 404 error.
http://wilmington.crimeboard.org/index.php/forum/unit-182f
GET /index.php/forum/unit-182f HTTP/1.1
Host: wilmington.crimeboard.org
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20100101 Firefox/16.0
Accept: text/problem-with-post-edit-buttontml,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
DNT: 1
Connection: keep-alive
Referer: http://wilmington.crimeboard.org/?page_id=702&wpvtax-neighborhoods%5B%5D=little-italy&wpv_filter_submit=Show+me
Cookie: sforum_8c94bf0302c53b11163c1fd8e26763f8=admin; wp-settings-1=editor%3Dhtml%26hidetb%3D1%26align%3Dcenter%26wplink%3D1%26urlbutton%3Dfile%26imgsize%3Dmedium%26galfile%3D1%26galcols%3D2; wp-settings-time-1=1349387778; fc=fcVal=7025075276256134976; wp-settings-time-12=1343272489; wp-settings-time-13=1343272788; expected_tab=google; welcome_info_name=Brad; wp-settings-time-14=1344720741; wpcfActiveEditor=content; wp-settings-14=mfold%3Df; wp-settings-time-20=1345498657; __g_u=288431185462537_6_1_0_5_1349389701294; wp-settings-time-23=1347304900; frm_form6_8c94bf0302c53b11163c1fd8e26763f8=2012-10-19+04%3A13%3A09; wp-settings-time-24=1347800773; wp-settings-24=mfold%3Do; terms_user_8c94bf0302c53b11163c1fd8e26763f8=agree; terms_user_date_8c94bf0302c53b11163c1fd8e26763f8=2012-09-29+22%3A26%3A36; wp-settings-time-30=1349028093; __utma=262216458.1816225778.1349207128.1350619219.1350632047.76; __utmz=262216458.1350361845.53.2.utmcsr=facebook.com|utmccn=(referral)|utmcmd=referral|utmcct=/l/rAQHiaf4cAQHutGiXXakchoDLeP0cAt86sj63uqxoq5ADgg/shar.es/5BDZ5; __unam=50f2a73-13a23058171-4303a36d-873; forumlist1=open; wp-postpass_8c94bf0302c53b11163c1fd8e26763f8=%24P%24B5f20GbYyAGwg2TDItYVnsMJmo49wP.; wp-settings-time-39=1350575163; PHPSESSID=3790c0778421127810adeaed1d207884; wordpress_test_cookie=WP+Cookie+check; __g_c=w%3A0; __utmc=262216458; wordpress_logged_in_8c94bf0302c53b11163c1fd8e26763f8=admin%7C1350792014%7C2865489e071516253761f3268964ff9d
If-Modified-Since: Fri, 19 Oct 2012 09:05:24 GMT
Cache-Control: max-age=0
HTTP/1.1 404 Not found
Server: Zeus/4.3
Date: Fri, 19 Oct 2012 09:30:23 GMT
Connection: close
Cache-Control: no-cache, must-revalidate, max-age=0
X-Powered-By: PHP/5.2.17
Pragma: no-cache
Content-Type: text/problem-with-post-edit-buttontml; charset=UTF-8
Expires: Wed, 11 Jan 1984 05:00:00 GMT
X-Pingback: http://wilmington.crimeboard.org/xmlrpc.php
Last-Modified: Fri, 19 Oct 2012 09:30:23 GMT
Would this be worth trying: disable SimplePress, drop all SimplePress tables, restore corresponding tables from a backup taken when things were still working fine, then reactivate SimplePress?
I’m looking for ideas as to how to approach the problem, the objective being to restore the previous perfectly good functionality with the original permalink structure. Once everything is working again, I can work on making the permalink structure better by getting rid of the “index.php.”
I’m then going to migrate to a different server that supports mod_rewrite. Hopefully that will help keep all the moving parts moving in the same direction.
For now, I am concerned that if I switch to the default permalink structure it will break existing links in areas other than the forum.
What approach do you suggest, given that I have a make-or-break presentation of this site in a little over 48 hours?
Steve and Brandon, I’m sure this topic has worn out its welcome long since, especially with the permissions issue producing a wild goose chase on top of the original 404 issue. I hope you’ll stick with me and that Andy will be back from vacation just waiting to tackle a nice juicy problem like this.
Quick note. I changed your SP integration page from ‘about’ to ‘forum’ just to see what happened. Have changed it back to ‘about’ but do not know if this is what you expect…
I have read through this whole thread twice now and am just as confused an everyone else I am afraid.
I do have two questions though. I was under the impression that NO ‘pretty’ permalink structure would work with a Zeus server (out of the box) so I am unsure how or why your ‘month/name’ permalink can work. Do you know?
Secondly – what is putting the /index.php/ in the permalink structure options? Again – I thought this was not possible. Does WP put that in the permalink options or do you have something else that puts that there?
I am in the process of moving the site to an apache server that supports mod_rewrite.
I’ll post back when that’s done.
Interesting times indeed. Good news, the new server is up and running. More importantly, I can once again access the forums.
The permalink structure is still the PATHINFO format. I did see some plugins that are designed to facilitate switching permalink structures to a new structure while maintaining backward compatibility with the older structure.
Since the new server is running Apache, the road to pretty permalinks is clear, albeit still uphill.
Any suggestions or special considerations on making the change to pretty permalinks so as to keep SimplePress running happily ever after?
Brad
Good news indeed.
Basically it doesn’t really matter what permalink structure you choose for your blog. SP should be able to accommodate it. There are some structures that WP themselves do not recommend. The use of categories in the permalink, for example, is known to be resource hungry and requires extra SQL queries to resolve so it would be worth keeping away from that perhaps.
As you will notice, the permalink selected relates mainly to blog posts and not pages and the forum imposes it’s own structure so should be safe to use anything. But yes – SP and WP pages needs to know the structure in order to resolve it.
I do hope the transition was smooth and that all now settles down. I personally think you have done the best thing all round for your future site stability.
several post ago, I made the comment that your .htaccess was not writable… it needs to be for url rewriting… plus you apache install has to have the mod_rewrite module active…
Thanks for the reminders.
Is 644 sufficient file permissions for the .htaccess?
depends on php flavor and other things…
per: http://codex.wordpress.org/Using_Permalinks
If you want to let WordPress do this, you’ll need to give WordPress write access to the .htaccess file. The exact permissions necessary depend on your server setup. Try adding write permissions for the owner, then group, then world, testing after each change; once WordPress has edited the file successfully, don’t add any further write permissions.
After applying the permalinks, you should change the permissions to something stronger like 660 or 644 to prevent others on the server from potentially having access to it.
The plot thickens.
For some reason, my production site on the new Apache server is now exhibiting the same 404 error as on my old Zeus server. The hosting provider has confirmed that .htaccess is writable and that mod_rewrite is activated.
The production site was working earlier today. The production site was created from a backup of the site on the Zeus server from before the 404 problem first manifested. The production site began showing the 404 this evening shortly after two things happened.
1) The hosting provider created a development site, on a separate account from the production site. The development site was created from a backup of the site on the Zeus server after the 404 problem had manifested. The production site doesn’t seem to have been changed by any development site files or database.
2) On the production site, I inadvertently changed the WordPress Address and Site Address to the URL of my Zeus site under Settings >> General, but then I immediately changed them back to http://wilmington.crimeboard.org. Could this have caused a problem for SimplePress?
Any suggestions?
Thanks.