Forum Replies Created

Viewing 15 replies - 1 through 15 (of 27 total)
  • Thread Starter Cobb78

    (@cobb78)

    Thanks to those who’ve tried to help. Please bear with me, as I’m sure eventually we’ll get this figured out.

    Here is the text of one of the posts that will not go through completely. What you see in the box below is the maximum that it will accept. The next word in the post should be “each”. When I added that word (as a test) and hit “update,” it gave me the “page not found” error. But if I update without that word, then it works. All well and good, except it’s only half a post.

    Is there something in this (including the word “each”) that is causing some kind of error in wordpress?

    Almost everyone who has been driving very long has had this experience. Someone on the road in front of you is driving along with their turn signal on. For a few moments you prepare for him to slow down, because his turn must be coming up soon. But it doesn’t take you long to realize that the man in front of you has no intention of turning. He’s just left his turn signal on.

    He’s sending out a message through his forgetfulness: I may be signalling one way, but that isn’t really where I’m going.

    This is the way that more than a few Christians live their lives.

    They signal that they are going to heaven, but after a short time, others can see the truth.

    They signal that they are good, moral people, but those who look at them can see that’s not really the case.

    They signal that they are living out Christ in their lives, but anyone who looks very long sees that their mind isn’t on Jesus.

    I would wager to say that you see these turn-signal Christians frequently. They are the ones who assemble with the saints, but who are not engaged in worshiping God. They are the ones who text while in the pews. They are the ones who pay little to no attention to the lessons. Oh, but they are there! They are signaling “I am a Christian” by showing up, but their actions don’t match up with it.

    You may think I’m being unfair and harsh. Please read on.

    I fear that all of us become turn-signal Christians at one point or another–even if it is just for a short time. By that, I mean that there are times when

    Thread Starter Cobb78

    (@cobb78)

    And, just to be certain, I am receiving the exact same problem on these posts when using Google Chrome as the browser.

    It’s quiet out here…

    Thread Starter Cobb78

    (@cobb78)

    This error just came up:

    TypeError: document.getElementById(…) is null

    Thread Starter Cobb78

    (@cobb78)

    Just to make sure it wasn’t some hidden formatting in the text I was pasting, I pasted it in plain text, and am still dealing with the same problem.

    Thread Starter Cobb78

    (@cobb78)

    Also have eliminated the possibility of the word count being too high (it stopped posting at 316 words, but others post just fine at 576 and above).

    Thread Starter Cobb78

    (@cobb78)

    And after more testing, I have discovered (at least on this one post) that I can post/edit half of the post, and it will work. I started adding a sentence at a time, and updating, and it worked a couple times. But then I got to the words “So, if we forgive in word only,…” and it wouldn’t post, and I got the same error as before.

    This is extremely frustrating.

    I’ve cleared my browser cache as well (in case that were to be suggested). This same problem exists in Palemoon, and wasn’t an issue until the past couple days.

    Thread Starter Cobb78

    (@cobb78)

    I can post a short post, with the title “Test” and the body of the post being “this is a test.”

    Is there some text that is somehow setting off problems? Is that even possible?

    Thread Starter Cobb78

    (@cobb78)

    “error404 logged-in admin-bar masthead-fixed customize-support”

    That error shows up when using Firefox’s built in inspector.

    Thread Starter Cobb78

    (@cobb78)

    OK, here’s what I’ve done thus far, and I’ve now eliminated several possible problems.

    I copied/pasted all the posts and pages from my website to a MS Word document, and completely removed WordPress. Nothing remained of it at all.

    Afterwards, a brand-spanking new fresh install of WordPress was done. I have spent the last couple hours creating new posts (pasting them in from the aforementioned MS Word document). And now the problem that I started off with (unable to post new posts or edit old ones) has popped up again.

    And before you ask, here’s some of the facts:

    *I am using the default twenty-fourteen theme with ZERO modifications. Therefore, this proves it has nothing to do with the theme.

    *I have installed ZERO plugins. There is nothing but the WordPress install. Therefore, this proves it has nothing to do with the plugins.

    *This is a brand-new install of WordPress with a brand-new database, thus it proves it is not an issue with a corrupted database.

    It worked just fine until I pasted in an article (which, by the way, worked just fine when it was posted originally almost a month ago).

    The Website is https://www.TheCobbSix.com, and it is hosted by Doteasy.

    The only things included in any of the posts are text, links to other posts on the same website, and some featured images (hosted on the website itself).

    Thread Starter Cobb78

    (@cobb78)

    3.9.1

    database was backed up yesterday afternoon.

    Thread Starter Cobb78

    (@cobb78)

    Any idea how I might go about fixing that? The link suggested by Evan contained two different approaches to repairing databases, and I did both of them. Still the same problem.

    I’m open to any suggestions.

    Thread Starter Cobb78

    (@cobb78)

    I did create a post after deleting everything. odd…

    The host is DotEasy.com

    Thread Starter Cobb78

    (@cobb78)

    Even after a fresh install of WordPress 3.9.1, and re-importing the database, it still will not let me edit a post or create a new one.

    Once again, just to make sure it’s clear:

    I’m using the default theme, all the plugins are fresh installs, updated, and there are zero old plugins on the server.

    When no plugins were activated, it still had the same problem.

    I CAN, however, do the “quick edit” feature and change the tags/categories. But that won’t work for editing the post itself.

    If this is a database/permissions issue, how do I fix it? I tried the above suggestion, and the problem still existed afterwards.

    Thread Starter Cobb78

    (@cobb78)

    Found the problem. It was the table prefix that had to be changed. The posts are back.

    Thanks for putting up with me.

    Thread Starter Cobb78

    (@cobb78)

    I marked the other one as [resolved], seeing as I’m starting over from scratch, no longer having the other problem.

Viewing 15 replies - 1 through 15 (of 27 total)