March 3, 2009 – Still Having WordPress Problems
|
| I suspect that the site is too big for WordPress. Although I had solved the problem yesterday, it re-emerged as I continued to port pages over. I was able to move about 2/3 of the entire site before WordPress’ capabilities were exceeded. I am still ‘locked out’ of page functions with a “500 Internal Error” on the php code, but I can transition the site back to the old format, and still keep WordPress for the news. Thank goodness I never implemented anything in WordPress without implementing it in my HTML first.
|
| The good news is that the attempted WordPress port spurred me to add magazine details, increase the cover scans, and clean things up. Those benefits will continue.
|
| Of course, I do continue scanning, and have some new stuff on the way. |
|
![[Model I]](../../../../images/computer-model1bx150.png)
ref: http://techfilipino.com/2009/01/internal-server-error-500/
Internal Server Error 500: Seen this recently?
By Francis Simisim
January 26, 2009
I’ve started experiencing an “internal server error 500? in my WordPress blog recently, all I did was update a recent post. I’ve checked around different solutions (one was saying to make a php.ini file where you type memory = 20mb) to solve the problem, yet none of it worked. I’ve tried a lot of solutions including deleting plugins and themes and still no success.
Then I remembered the ‘Stealth login plugin’ which when locked out of the system, delete HTACCESS in wordpress folder.Which I tried and surprisingly it worked, it’s really a weird solution but it got my blog online again.