Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • I was looking for an answer to this as well, I don’t want my email password to be visible in the plugin settings.

    I had the exact same problem and I did find a way to check that it’s the same theme before updating:

    So I’m using Craft by Themetrust with a child theme, saw that there was an update available and clicked “update now”, and my website became an unrecognizable mess.

    Luckily I had made a backup before doing updates and was able to restore the original Craft theme!

    Now when I go back to the Themes overview in the WP backend, I see that if I click on the the theme’s thumbnail to see the “Theme details”, in the box labeled Update Available, if I click on “View version details” then it’s evident that it’s a totally different theme by a different author, not Themetrust.

    It would never have occurred to me to look at the version details before updating to make sure it was the same theme, but it’s definitely worth checking in the future, especially if the theme has a one-word title that’s likely/possibly used on a completely different theme.

    Hope this helps someone else with the same problem!
    And always make a backup before updating!

    Thread Starter zwaan

    (@zwaan)

    Thanks for replying!
    Sorry, I meant on the backend, when I’m entering Up-sells and Cross-sells for a new product. Does anyone know if this feature has been removed from the Woocommerce update?

    These are 2 things I noticed in the HTML for the backend that seemed like they might be clues (shown in larger HTML context below):

    style=”width: NaNpx;”
    style=”width: 0px;” autocomplete=”off”

    …and this is from the CSS that’s showing in the site inspector for the Up-sells and Cross-sells input boxes:
    element {
    width: 0px;
    }

    //***HTML***//
    <p class="form-field">
        <label for="crosssell_ids"></label>
        <select id="crosssell_ids" class="ajax_chosen_select_products chzn-done" data-placeholder="Search for a product…" multiple="multiple" name="crosssell_ids[]" style="display: none;"></select>
        <div id="crosssell_ids_chzn" class="chzn-container chzn-container-multi" style="width: NaNpx;" title="">
            <ul class="chzn-choices">
                <li class="search-field">
                    <input class="default" type="text" style="width: 0px;" autocomplete="off" value="Search for a product…"></input>
    
            <div class="chzn-drop"></div>
        </div>
    </p>

    [Moderator Note: Please post code & markup between backticks or use the code button. Your posted code may now have been permanently damaged by the forum’s parser.]

    Thread Starter zwaan

    (@zwaan)

    Hello again, I managed to solve the issue!

    In case anyone gets the same error message, my mistake was that I had pasted the url into the Page ID field instead of just the numbers. That fixed it, posts are now showing where they should be!

    Thread Starter zwaan

    (@zwaan)

    Update: I kept searching online and found this article:
    https://blogging.nitecruzr.net/2011/02/referer-spam-is-needlessly-alarming.html

    The highlights:
    “blog owners who spend time perusing the Stats “Traffic Sources” display are finding odd entries there and are becoming needlessly alarmed. …blog owners who scan their access logs would see an unknown URL, click on it, find themselves on a new website – and might become the website’s newest customer … Spammers have developed techniques for automating surfing. Stats records the initial hits, and saves the referer URLs. We look at the Stats displays, and wonder.”

    And indeed I did find a flurry of spam comments caught in my spam filter.
    So I guess it’s just a nuisance rather than a security breach, but thanks anyway, I’m still glad noticed it in the stats reports and investigated.

    Thread Starter zwaan

    (@zwaan)

    Hello, I contacted my hosting company to ask about this and they sorted me out with a new log-in url. Solved!

    Hi, just curious, is the theme updated very often? Would it not be just as easy to change the text again if it reverts to ‘comments are closed’ after an update?
    Or is there another issue that I’m missing?
    I’m fairly new to WordPress and have not yet investigated ‘child themes’; that’s the only change I made in the code.
    Thanks!

    I don’t know if using a child theme would make a difference, but I just changed this on mine by going to Appearance > Editor. Under “Templates” on the right side bar, click on “Comments” to see the comments.php code, find the words “Comments are closed.” and change them to whatever you like!

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