Forum Replies Created

Viewing 15 replies - 1 through 15 (of 17 total)
  • Thread Starter dsmythe

    (@dsmythe)

    I received the CRON job mails saying it cleaned out a number of expired tasks which lead me to look at the expired events settings. Apparently all the tasks were being deemed “expired”. I checked the box in settings to “show expired tasks” and I was able to then see tasks which had been signed up for. And now it seems to be working as you would expect. I am not sure a date got corrupted somewhere? My test event was definitely in the future.

    I have to look through the documentation more to see if I can find more about expired tasks and how they work. Anyway. Seems to be working now. Thanks for the responses.

    Thread Starter dsmythe

    (@dsmythe)

    With regards to: “Also, you say the sheet details shows 1 filled spot, but then also say that the sheet details shows all tasks as empty.”

    Correct, there is a mistake there. “Sheet Details” (the detailed listing of all tasks) shows no evidence of the tasks being registered for, while “Sign Up Sheets” (the listing of All Sheets with summary sign up status in the columns to the right) shows tasks filled.

    Essentially, user gets an email saying they’ve signed up, but there’s no record of that in the Sheet Details.

    I tried to use both settings “Filled” or the Name… Neither resolved the issue.

    Thanks for your response.

    Some thoughts:

    Pick the right theme. One with multiple sections (headers, footers, sidebars, etc) works well as they allow you more flexibility for images and widgets.

    Use pages rather than posts for your content.

    Remove all the comments sections from your pages.

    Pay attention to what you put in sidebars, remove the login, RSS and meta sections for example.

    Tie your pages to your menu for navigation.

    https://en.support.wordpress.com/using-wordpress-to-create-a-website/

    You change the star to something else in the “Character Icon Name” field at the bottom of the Header Options page. You choose a new icon from the list at https://fortawesome.github.io/Font-Awesome/icons/

    See Web Applications section.

    So if you wish to have the camera. Enter “camera-retro”

    Make sure you are running the latest version. Early versions had problems with older IE Versions.

    Are you saying you don’t see them at all? Or that you want more options?

    They come from the title-meta.php file.

    I don’t think there’s a control panel option for changing this.

    I pulled all of this:

    // check for XSS attacks - we disallow any javascript, meta, onload, or base64
        if (preg_match("/.*(script|onload|meta|base64).*/is", $email)) {
          echo "possible XSS attack - ignoring email\n";
          continue;
        }

    I ended up just pulling the entire section of code because, like others, I could not see what was in the plain text mails that was running afoul of the new code. I did @joyfulart’s suggestion to check/add the user to no avail. I made the change using the plugin editor within WP by commenting out the lines. (// in front of each)

    Probably not the best solution and I’ll continue to follow this thread hoping someone figures it out.

    Here is the postie test log after I removed the XSS code… perhaps someone can comment on what part of “script|onload|meta|base64” this might be running afoul of…

    **********************
    memory at start of e-mail processing:29427464
    Confirming Access For [email protected]
    posting as user 2

    Message Id is :<002101cd80de$30b9a420$922cec60$@[email protected]>

    primary= multipart, secondary = alternative
    primary= text, secondary = plain

    Post Author: 2
    Date: 2012-08-22 21:20:04
    Category: 3
    Ping Status: open
    Comment Status: closed
    Subject: Where Do You Find?
    Postname: where-do-you-find
    Post Id: 567
    Posted content:

    (large blob here of plain text looking email)

    memory at end of e-mail processing:29512368
    **********************

    Upgraded to the 1.4.4 and I am now getting this ‘no new mail’ issue. On Bluehost as well. This ran for years under a prev version and I was loathe to upgrade but did anyway.

    Anyone have anything new to add?

    The test works and does the connect. I verified that there is a mail in the box.

    When I run postie, it says no new mail… but then it deletes the mail that was there.

    Thread Starter dsmythe

    (@dsmythe)

    I’d report it… but I can’t get the submit report to work on…

    https://themes.wordpress.net/report/

    Won’t take ANY email address I have.

    I must be cursed lately!

    Thanks all!

    Are you sending plain text emails? HTML mails will add these formatting issues.

    I am with zammi that this is some sort of issue with TinyMCE. I upgraded another of the WP installs I admin and had the same issue.

    The only thing that fixes it is to turn off the WYSIWYG options (“Use the visual editor when writing” in the user profile). I removed all my plugins and the only way to post content was to turn off WYSIWYG.

    Success!!

    In regards to MichaelH’s question:

    2. If you look in the database table, wp_posts, what do you see in the post_content field?

    wp_posts are empty, post_titles are not empty.

    But in checking that, I just decided that this was probably going to take some time to get addressed seeing as no one has responded in a week. I just dumped a post directly into the database to see what would happen.

    That seems to have fixed it. I also turned off: “Use the visual editor when writing” in the user profile but this was after I was able to start posting again.

    Very strange.

    Has anyone figured this out?

    Does the Database user need to be addressed? Or the user within wordpress (the administrator, editor, etc). I am leery of doing anything with the db user.

    I don’t see using Phpadmin how I can change the user rights for the dbuser (version 2.6.0).

    Thread Starter dsmythe

    (@dsmythe)

    In the template-functions-link.php file:

    I changed
    $page_modstring = “page/”;
    to:
    $page_modstring = “?paged=”

    $index = ‘index.php’;
    to:
    $index = ‘.php’;

    From:
    $qstr = trailingslashit($qstr) . $page_modstring . $pagenum;
    to:
    $qstr = $page_modstring . $pagenum;

    and now it appears to work.

    I probably overwrote something critical, but it works now (until I find that it doesn’t).

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