Support Forum
so unix, which was the real question
Visit Cruise Talk Central and Mr Papa's World
Ah, yes, Unix it is.
Digging into permissions, I have my WordPress installation in the directory /dev. When the forum 404 issue arose, I created a new FTP user account with access to dev as the top level. This may have compounded the problem, as I see now that the owner for everything under dev is now wpadmin instead of tutorsys. I didn't explicitly make that change, but it seems the host's account creation process does that.
I notice that the owner / group for everything above the /dev directory is tutorsys tutorsys.
However, the owner /group for everything below /dev is wpadmin tutorsys.
Also, permissions are 644 for a lot of the files below /dev and 755 for the directories. Might this be a problem?
Until the wpadmin account was created, everything was tutorsys tutorsys.
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.o...../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.o.....it=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.o.....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.
1 Guest(s)