Forum Replies Created

Viewing 13 replies - 1 through 13 (of 13 total)
  • knowtown

    (@knowtown)

    genej313,
    I completely agree with you about Bluehost. I read others in these forums with some complaints but I cannot say enough good things about Bluehost. Best support I have ever had with any host provider!!

    I converted one fantastico install and two manual installs to the simple script installs today and had not one major problem. Was much easier than I was expecting.

    The only minor problem I had while following the instructions was when I finally got to the upgrade. The instructions had me install the current version I was using (2.5) and then after it was installed using the simple script version to run the install and in two cases it will not let me complete the upgrade to 2.5.1. On the last one I decided to just try to go straight to 2.5.1 and it seemed to work. From the simple script page it shows I am at 2.5.1 but when I log in to the dashboard it only shows 2.5 and will not let me upgrade.

    I have no doubts whatsoever that the excellent support at Bluehost will be able to eventually help me resolve this. And all my sites are up and fully functional at 2.5.

    I wonder if you had any similar problems?

    Thread Starter knowtown

    (@knowtown)

    Thanks everyone for the suggestion to upgrade. I completed the upgrade succesfully But the problem still occurred. While thouroughly testing I think I found the culprit. The issue is being caused by one of the plugins I was using (Scripturizer 1.5). I thought I had tested all my plugins before but I must have missed this one. I started testing each plugin one at a time and this one brings on the problem every time. I am not sure what it is about that plugin that was creating the problem but now that I have disabled it, I think all systems are go.

    Sorry for wasting everyone’s time for a simple test that I thought I had already done. I do appreciate all the help though.

    Thread Starter knowtown

    (@knowtown)

    No worries vkaryl. And thanks a ton for your help. You were tremendous.

    Thread Starter knowtown

    (@knowtown)

    I tried quotemark replacer and unfancy quote with no success. Apostrophes still create the error. Double quote marks does not create the error so it is limited to only single quote (apostrophe).

    Thread Starter knowtown

    (@knowtown)

    I will certainly give this a try but while looking it seems to me that most of these issues that surround curly quotes are exactly the opposite of the one I am having. If I am reading correctly most people have problems when they cut and paste from Microsoft Word into WordPress. I however have success when pasting from Word and not when using WP itself. If the apostrophey looks like the curly quote I get no error. If it does not look like a curly quote I do get the error. So I am not sure I want to disable them. But I will try a couple of different plugins and see what results I get.

    Thanks for the tip.

    Thread Starter knowtown

    (@knowtown)

    Yes, I have googled this issue and not found anything. There were some distantly related issues with SQL and apostrophes but none of those ideas helpd this case.

    Here is one more interesting thing I just discovered. The problem occurs at the moment the autosave kicks in. after that the error pops up at every auto save and the final publish. However, if I type every think in a word processor and cut and paste it into WordPress and publish before the autosave happens the post publishes with no error.

    I will forward this info to my host provider to see if they have any ideas.

    **UPDATE**
    Actually, when I went back to look at it again the text that I cut and paste from my word processor displays the apostrophy with the look of a comma (the dot with the curl coming down) but the apostrophe when typed within WordPress displays as a straight line. The character is actually a different character. The one from the word processor does not generate an error but when typed within WordPress it does.

    Does anyone know how to change this?

    Thread Starter knowtown

    (@knowtown)

    OK. So I heard back from my host provider tech support team:

    The collation on all of your WordPress databases is currently set to “latin1_swedish_ci,” which is the MySQL default. The latin1_swedish_ci character set should work without issue for any English character storage. We have numerous WordPress installs on our servers (including my personal blog) and I haven’t seen this issue previously. I am going to research the issue a bit further, but it seems you may have encountered a bug in WordPress that is exclusive to your environment/account. I see that you have an installation of WordPress that was installed by Fantastico– do you have the same issue with that install?

    I have two blogs running WP 2.1.1 and they are both having this same issue with the apostrophe creating a syntax error. One was a fantastico clean install with a brand new database and the other is an existing blog that I recently upgraded to 2.1.1. But I also host a friend’s blog on this server in a different folder with its own database. That blog is still running 2.0 and it is not having the issue. So somewhere there is a strange issue with my two 2.1.1 blogs on my server. Not sure what is causing the differnce. If I hear anything else back from my host provider support I will let you know. In the meantime, I am stumped. If anyone knows why my apostrophes are working differently in 2.1.1 than they did in 2.0 and wants to throw me a bone I would appreciate it.

    Thread Starter knowtown

    (@knowtown)

    Thanks again. That is helpful. And I have an excellent host provider so I think this will work. I will post after I talk with them.

    Thread Starter knowtown

    (@knowtown)

    vkaryl.

    Thanks for your reply. I put it in a clean database for the new install.

    James

    Thread Starter knowtown

    (@knowtown)

    I just created a brand new blog in a different subdirectory and I am having the same problem. This was a fresh install. I am wondering if this could be something wrong with my SQL database?? Any one have any ideas on if something in the SQL database could cause the apostrophe problem I am having??

    Thanks for any help.

    James

    Thanks Chuck. That certainly gave me some new ideas to look at. I appreciate that.

    I tested the default themes and I get the same results. I wish I knew what changed in how firefox processes the new-post page in 2.1 differently than it did in 2.0.7. For now I can function by limiting my writing new posts to my MAC and using Safari because that works fine. But if anyone has any ideas on where to look in Firefox to resolve this I would appreciate it. Thanks

    update…
    On my Linux (Suse 10) computer the only browser I have installed is Firefox and I cannot save/publish new posts. I get the message that says “are you sure you want to navigate away from this page? all information will be lost…”

    If I click continue then my the entry will save/publish with only the title. The contents of the post itself are gone. So if I choose publish I get a title on my blog but no content in the post. This seems to be only firefox browsers for me regardless of the OS I am in.

    If I use IE on a PC or Safari on a MAC things work ok. I will try to find out what is different in Firefox with 2.1 and 2.0.7 and post what I find out. If anyone else has ideas I would love to hear them.

    Thanks again.
    James

    I am having similar issues. I do not get the stack overflow error but I do get the “are you sure you want to navigate away from this page?” question. If I cancel it takes me back to my post. If I continue it saves or publishes the title of the post but not the post itself.

    Here is what I find so far. On my MAC (10.4.8) if I use Safari the post will save/publish with no error so I am assuming things are fine at the host server level. The only strange thing I get with Safari is that my WP-Amazon plug in will not work unless I save the post and then edit it. On a new post the “insert from Amazon” option is not available. However, When I use Firefox or Camino I get the “are you sure you want to move away from this page” message.

    On my PC I get similar results. Things work in IE but not in Firefox.

    Since it works in safari(MAC) and IE(windows) I assume that the problem is not with WordPress 2.1 but with Firefox. I have cleared cache and that helped bring back the editor toolbar buttons but I still cannot save a post in Firefox.

    Anyone have any ideas what could be causing this only in Firefox? I had no problems with WP 2.0.7. The only change has been the upgrade to 2.1.

    Thanks,
    James

Viewing 13 replies - 1 through 13 (of 13 total)