justinbaeder

richard-
you can conditionalize the plugin call before disabling it, so it won’t break the site (unless it’s something monstrously complex that I’m not thinking of). Instructions:
https://www.webbleyou.com/preventing-plugins-from-crashing-your-blog

I posted this on another thread, but I’ll say it here too since this one is newer.

I was posting the other day, and my browser crapped out and said “Server not found.” I hit refresh, and the site was indeed there (just a random glitch, or perhaps my internet connection hiccuped for a second). But my post was gone. I hit “back,” and my post was still gone. History.

Today, I was using Gmail, but wasn’t connected to the Internet. I wrote my message and hit “send”, not remembering that I wasn’t connected. Gmail noticed, and told me I was offline without losing the message. This is built in via Ajax. I connected, retried, and my message sent.

I’m sure the lost post scenario has happened thousands of times to thousands of people – every one of us has lost a post, no doubt. Even if you save drafts frequently, you’re still relying on an HTML form submission to save your post, which can be messed up by a number of things. Ajax-ifying the WP write interface would allow WP to confirm that a connection is available, send the post data, and only reload the page after it received confirmation that the post was saved. It may or may not be faster (e.g., compare gmail to hotmail), but it would be a lot more reliable.

jalenack-
On the contrary, I think having an Ajax posting interface would be immensely valuable. Allow me to illustrate.

I was posting the other day, and my browser crapped out and said “Server not found.” I hit refresh, and the site was indeed there (just a random glitch, or perhaps my internet connection hiccuped for a second). But my post was gone. I hit “back,” and my post was still gone. History.

Today, I was using Gmail, but wasn’t connected to the Internet. I wrote my message and hit “send”, not remembering that I wasn’t connected. Gmail noticed, and told me I was offline without losing the message. This is built in via Ajax. I connected, retried, and my message sent.

I’m sure the lost post scenario has happened thousands of times to thousands of people – every one of us has lost a post, no doubt. Even if you save drafts frequently, you’re still relying on an HTML form submission to save your post, which can be messed up by a number of things. Ajax-ifying the WP write interface would allow WP to confirm that a connection is available, send the post data, and only reload the page after it received confirmation that the post was saved. It may or may not be faster (e.g., compare gmail to hotmail), but it would be a lot more reliable.

Great – just keep in mind, the Wiki page you linked to explicitly says that it’s not the best solution, as that page is over a year old and was written for 1.2x.

Aziza-
It sounds like you have the < ?php sem_sidebar_tile(); ? > function in two places – once in the index, and once in the sidebar.php file, which is otherwise empty. You only need it in the one place. I know the semiologic theme has some weird custom stuff, and I don’t know exactly how it works, but I think Denis is right – there has to be some content somewhere, or there’s nothing to display.

My guess is that you want the < ?php sem_sidebar_tile(); ? > function in the main template, and the sidebar content in the sidebar.php file. Does the semiologic theme have another file for holding the tile contents?

saxeine-
Do you mean it gives a 403 error when you try to save the post? I’m guessing some of the files in wp-includes may not have their permissions set properly, especially the file or files that validates post contents, hence the error when you incorporate HTML. But if you’ve checked that, I don’t know.

Sorry to ask a potentially insulting question, but you’re using HTML, and not BBcode or wiki formatting, right? Just trying to think if things that could throw off the tag-closer/validator.

I had this problem just now (first time in a long time; I run WP on over a dozen sites), and was perplexed.

The problem was that I typed the /wp-admin/link-add.php url directly, as I am prone to do. Apparently WP doesn’t like this, so I visited the wp-admin page first, then clicked the link-add button. It works now.

Of course, I also went through the above steps, so try that stuff too.

I had the same problem – I had renamed wp-comments-post.php in an effort to reduce comment spam, and kept my modified 1.2 template when I upgraded to 1.5. Deleting the extra file and changing the comment-posting code in index.php fixed it.

Tamba’s solution is a general wp/PHPMyAdmin tutorial, and does not work in this situation because the buggy code in wp-login.php will just overwrite whatever edits you make via PHPMyAdmin, as the link to the other thread above says. This happened to me, and continued happening until I commented out the code in wp-login.php. See:
https://www.radicalcongruency.com/20050124-no-style-at-all

I’m running 1.3-alpha-5 and just started getting the same thing (though I’ve been running this version for several weeks). I’ll try fixing it using Tamba’s directions.

It’s likely a mod_rewrite issue. Paste in your rewrite rules from the .htaccess file and people may be able to help.

I’ve posted this on several threads so that people using the CVS releases will see this problem…
I’m using 1.3-alpha-3, and I get an “empty delimiter” error when trying to use posts_nav_link. Not sure what the deal is.

I am having the same problem, but when I insert post_nav_links(); I get a URL that is apparently an error message, so the link takes me to this URL:
https://www.radicalcongruency.com/<br%20/><b>Warning</b>:%20%20Empty%20Delimiter%20in%20<b>/my/blog/home/wp-includes/template-functions-links.php</b>%20on%20line%20<b>456</b><br%20/>https://www.radicalcongruency.com/page/2/
I think all my rewrite rules are correct; it’s the link that’s generated that is messed up. Any word on whether this is a bug? I’m using WP 1.3-alpha-3 from an Oct CVS.

Just curious…why are you installing wp blacklist? This feature is built into 1.2.1 Mingus, right?

1.3’s current nightlies don’t work with AMM 1.1 because of the way the DB info is called. Denyerec has sent me the code changes, and is working on an updated release.