Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter lars-eighner

    (@lars-eighner)

    Damn! It was a stray umbilical Template: to a once-parent.

    Forum: Fixing WordPress
    In reply to: Site Down

    Your error message is:

    Parse error: syntax error, unexpected ‘<‘ in /home/vg007web04/53/56/3015653/web/wp-content/themes/gridspace/functions.php on line 151

    You will have to look at your function.php file. This is likely to be a stray < within php tags. If you had an extra < in text, it might wreck you theme but you would see something. Perhaps you have forgot to quote stuff in an echo line.

    google site verification, if that is what you are talking about, goes in a meta tag in the header. But this a php problem.

    Exactly the attitude I got at the time. He’s never made a mistake. He now defines the what the “basic plugin” is and what are the pay features, without having made his personal view public while users who thought they were using the basic plugin were testing the now pay features for him. For a long time it was only possible to contact him through web form and forums on his own site – and now it becomes clear that he did want email evidence of his perfidy to be available later.

    I did not experience great support when I was unwittingly used as a beta tester years ago. The author had named a table column for what became a reserve word when MySQL upgrades. The author seemed not understand the problem and became very rude. I had to hack to get his plug into work. Eventually he upgraded MySQL and realized what he had done, but I did not get a word of apology.

    Thread Starter lars-eighner

    (@lars-eighner)

    I have rechecked everything.

    The problem is plugin Captcha version 2.33.

    When it is deactivated the dashhoard is normal and everything else is normal.

    I have checked the settings for this plugin and I do not see any setting that appears more suspicious than any other.

    This plugin is frequently updated. Apparently the last time I logged in, I updated the plugin to a broken version and logged out without returning to the dashboard to see that it had been broken by the plugin update. I have no record of the last version that worked.

    Background images set in stylesheets are relative to the stylesheet.
    If your styles are in your theme then the right path is
    “images/mybackground.gif”

    But IMG SRC in documents must have a path relative to the document.
    In the case of wp documents that would be ‘path-to-wp/wp-content/themes/yourthemename/images/yourpic.jpg’ if you really want to keep your images there.

    path-to-wp/ might be nothing if you installed wp in your web root directory, or it might be blog/ if you installed wp in a subdirectory called blog. remove the slash too if path-to-wp/ is nothing.

    It is often more convenient to have your content images in their own directory. So wherever wp is, you can create a directory for your content images in that directory. then src=’images/mypic.jpg’ will be right and it will be right even if you change themes.

    Thread Starter lars-eighner

    (@lars-eighner)

    Well, maybe. I don’t see and HTML tab here. There is one when I edit a post as admin. but even though I can put tags in the editing box. They still get sanitized out, along with many attributes, and
    BR the break
    element still gets inserted
    wherever
    there is a newline
    like this. All white space should
    be exactly the same and
    the equivalent of a single letter-spave

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