Yes, you want to download the file to your computer. Make a copy, just in case. Then open the original with a text editor and make the change and re-upload (replace the file on the server).
The backup is the most important step, in case something goes wrong you have something to roll back to.
Okay, I did that and it really was easy to find the means to open the file via a text editor. So, at least now I know how to do that! š
And I’ll be sure to have a backup too.
It’s certainly a very long file, but I should be able to succesfully tweak it and then, cross my fingers in hopes that the tweak will fix the issue. Seems funny that any other small drafts do save just fine.
Will let everyone know what the outcome is…just in case another user runs into the same problem. š
You *don’t* want to edit core WP files. You will loose the changes once you upgrade.
Increase memory for php by putting this near the top of wp-config.php
define('WP_MEMORY_LIMIT', '64M');
and see this post: http://wordpress.org/support/topic/320207?replies=3
AHA! Thanks, SDT. All righty. Let’s try this approach.
I did change the wp_settings file, and yes I do have a backup of the original file. The only change was the number, I just carefully altered the ’32’ to ’48’. I should be able to fix it back again w/o any worries. I will do so, since the change didn’t do a thing to help the issue. I can still easily save ‘test messages’ but nothing lengthy.
Umm…OK…I have the file open in notepad. But where, exactly, should I paste the two changes- I’m willing to try both! So anxious to make my dot Org blogsite a success.
define(‘WP_MEMORY_LIMIT’, ’64M’);
AND-
ini_set(‘pcre.backtrack_limit’, 1000000);
Like this:
<?php
define('WP_MEMORY_LIMIT', '64M');
ini_set('pcre.backtrack_limit', 1000000);
/**
* The base configurations of the WordPress.
Someone in another slug suggested the memory-bump plugin http://wordpress.org/extend/plugins/memory-bump/
@wprelief: wp-config.php is not a core WP file and it’s OK to edit it.
ARGH! I pasted in the tags but when I go to save the file, all the formatting disappears. Why is it doing that? Would it still function even with the formatting gone?
OK, I pasted it here to show what I mean. Now it’s partly formatted but still looks strange. Will that matter?
[Large code excerpt remove by moderator. Per forum rules, please post all large code excerpts in the pastebin, and censor your database login details this time.]
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Are you using a plain text editor to edit the file?
Since wp-settings has the check to see if WP_MEMORY_LIMIT is defined, you could in fact just drop the suggested code above into your wp-config.php file.
Sorries about not using ‘pastebin,’ I forgot!! š
MacManX, yep, I’ve been using Notepad to edit the file. Tried it with NotePad++ and an oldie but a goodie, NoteTabLight. Still same results, formatting gone. Weird that it would *partly* come back when I pasted the contents in a post here. Is there another means of keeping formatting while tinkering with a file?
Saw the plain text editors link…it includes Notepad++. I presume there is a ‘special’ means of editing php files there without messing up as I’ve done, lol
wprelief, how would I do that, plz? –‘just drop the suggested code above into your wp-config.php file.’ I thought that was what I was doing, at least on the latest attempt before ftp’ing back.
Last nite I did replace the file thru ftp. AND got a fatal error! EEeepp. Something to do with ‘line 15,’ not sure what that’s about.
Was hoping the original “try” in the wp_settings file would do the job. It was really easy tweaking that one. But ‘config,’ not so easy!
OK, tried fixing ‘config’ with Notepad++ and apparently the formatting did not change. Uploaded to my subdomain. Tried logging in. Got the same fatal-error msg only this time it’s for Line 1. Here it is:
Fatal error: Call to undefined function phpdefine() in /home/seaymee/public_html/aeolusia/wordpress/wp-config.php on line 1
I thought we couldn’t “break” WP…it looks like I did! -lol
You’ve got something wrong in wp-config.php. Did you delete the starting <?php at the top of the file? Or the semicolon at the end of
define('WP_MEMORY_LIMIT', '64M');
OH…no, I didn’t. I thought the starting characters were meant to stay in there. Thought the semicolon was also ‘supposed’ to be there too. So should I be deleting those or not?
Most of my online probs are basically simple blunders. This should be, too, if I can tweak things JUST right…
I could attach the current version of the file here, if that would clarify matters.
ASAP
No, the characters stay there. Paste your wp-config.php in WordPress Pastebin and delete your password and login out of it and then link pastebin here.
I didn’t see anything that needed removal, and it did post me as “Anonymous,” so I guess I’m safe…!
Here ’tis… Somehow it don’t look “right” to me, so much double spacing. But this is straight from Notepad++. Now it has enumerated lines, something it didn’t have in my editor.
http://wordpress.pastebin.com/JqdagaDL
Oh and I put back the original php file stored in Downloads. The edited copy was saved somewhere else. And now, my WP is working again…except for this one huge problem! =(
