anklebiter
Forum Replies Created
-
Forum: Plugins
In reply to: ViewLevel 1.1 ReleaseGo through the WP code and change all the minimum user levels for posting access. Since this isn’t something that is centrally managed in WP, there’s no simple way for a plugin to do it for you. Time to get your hands dirty in the code. ??
Forum: Plugins
In reply to: skewed levels in ViewLevelThe only way I was able to get around this issue was to actually modify the WP code that sets which user levels have what privileges. It’s not centrally defined in WP (at least, not through 1.2- I haven’t upgraded to 1.5 yet), so I had to go through the files to find the places where privileges are defined. I changed everything to level 8 to even see the options to post/edit/add links/etc. in the admin menu, and I changed the actions when a “publish” button is clicked, for example, to check that the user had at least a level 8 (rather than a level 1) before allowing the publish to take place.
I don’t remember where all this stuff is found in the code, but it’s really not as hard as it sounds to find.
Forum: Fixing WordPress
In reply to: Modify headers- I searched, really I didHah, perhaps I’ll try that this weekend… the install might only be 5 minutes, but the tweaking is a nightmare…
(No, the files I’m having problems with were not the tweaked ones.)Forum: Fixing WordPress
In reply to: Modify headers- I searched, really I didI wasn’t explicit enough, I guess. My apologies:
1. I already tried to edit the lines mentioned in the error message, but there were no problems in the lines or files mentioned that I could detect. Also, the files mentioned in the error message have been working just fine for months and I didn’t edit them before the errors started. As I said, I did read the previous posts about this error.
2. I’ve already tried the freshly downloaded files. I replaced all the files mentioned in the error message, the wp-comments.php file I edited, and wp-config.php file.
3. I’ve already tried restoring wp-comments.php, and wp-comments-post.php is still called wp-comments-post.php because, as I said, I changed it all back.
And yet, I continue to get the error.
(Thanks for stopping by, macmanx…)