Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter hugme

    (@hugme)

    I just didn’t wait long enough. It turns out it was a problem with the google certificate authority. I thought they had changed some things which caused the plugin to not work any longer, it wasn’t a change though, the Google end was actually not working (possibly just for my account?) early this morning. I DID however send you some code this morning to add the the plugin. it doesn’t change any of the normal behavior but it does give you some better error messages when things like this occur. is this the best way to post things like that?

    Thread Starter hugme

    (@hugme)

    It has been resolved. When you cut and past something it automatically sets it for “preformatted” in word press. You have to go in and manually change the formatting.

    Thread Starter hugme

    (@hugme)

    I’ve found the problem. The module is putting in <pre> in front of the table. This is causing it to ignore the css I’m giving it for word breaks. Do you have a suggested way of removing the <pre>?

    Thread Starter hugme

    (@hugme)

    I fixed part of it. There needed to be a css change in the style.css for twentyeleven (and all the others). This entry:

    .entry-content td,
    .comment-content td {
            border-top: 1px solid #ddd;
            padding: 6px 10px 6px 0;
    }

    Needs this added:
    -moz-hyphens: auto;

    This fixes the ie/chrome vs firefox issue. However it does not fix the word break issue. “word-brek:” in the css seems to have no effect on it in table, tr or td.

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