In short- no. The html in question is hard-coded in the post_submit_meta_box callback function. You can, of course de-register the publish metabox and re-register your own which mimics post_submit_meta_box (but making your alterations) and being sure to keep the names of the inputs exactly the same. This method has been outlined the following posts where … Read more
disable all plugins or change theme to default one. AFAIK there is no such function by default in WP to redirect non loged in users to login page.
Your behavior is logical. the profile.php page is in the protected /wp-admin/ folder. the wp-login.php is in the root (/), which is not protected.
You need to wrap your code in either code or pre tags. code is for when inline code in a sentence e.g. include(“hello.php”) whereas pre is for preformatted blocks of text e.g.: function hello_world(){ echo ‘hello world’; } For code highlighting etc, you’ll need to look for plugins. The easiest way of using these tags … Read more
On the edit posts page, click on ‘Screen Options’ on the top right, and you can enter a value for the amount of posts per page.
Yep! Check out wp_editor(). It was a one of the big new features in WP 3.3.
What your seeing is probably a PHP fatal error, however your server will be configured to log them to the error log rather than present it on the frontend. To find out what the error is, check your error log, or alternatively, if you don’t have access to the error log or enabling the error … Read more
WordPress only uses the tables it creates upon installation. Technically WP wouldn’t have a problem with removing tables that are not in the created tables. However, messing with the tables in the mysql database is not necessarily the best for MySQL itself. Also, if you are trying to optimize MySQL by removing tables and databases, … Read more
This sounds like a Folder Permissions problems – the MAMP Apache user needs to have read/write privileges on everything under your Sites/wordpress/ folder. This is easy to do from the terminal … my post on Permissions should help can i run wp as root permissions
Solved: It appears chrome had a corrupt cache as I attempted to visit the backend on Firefox and noticed that the issue wasn’t there. I had to delete all Chrome browsing data (cache alone wouldn’t do it).