Forum Replies Created

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter ellen413

    (@ellen413)

    Hello, that stopped working. I can no longer save a draft if I temporarily rename the .htaccess ‘file’. Any more ideas? I’m kind of in a jam now… I tried my hosting provider, but they aren’t really too helpful… without my paying for a ‘fix’ – but the blog doesn’t make any money and I don’t want to spend money on this if….

    Thanks again,

    ellen

    Thread Starter ellen413

    (@ellen413)

    NEVERMIND this update. I reloaded the page, and cleared all cache, and it didn’t work anymore.

    Dear bcworkz,

    Another update, and it’s is really, really weird. I switched the temporary name back to plain old .htaccess, — and now the drafts are saving with the old name restored (still with the temporary theme).

    However, during this process I saw there are a few ‘.htaccess’ folders and I’ve asked my hosting provider why that is, since I’ve never dealt with any of these before. Might you have any idea why a temporary name switch would force it to work? Or why there are several of these folders – with different extensions?

    • This reply was modified 2 years, 5 months ago by ellen413.
    Thread Starter ellen413

    (@ellen413)

    Thank you for the ideas. It’s not the plugins or theme – I renamed the .htaccess folder and voila (!) I was able to save a draft. But now, I’m afraid the folder name messes up other things? What should I do about creating a new one with the proper ‘.htaccess’ name? I’m a little frightened at playing around with stuff beyond plugins…….

    Thread Starter ellen413

    (@ellen413)

    No. I haven’t seen it since I properly installed the plugin zip file.

    Thread Starter ellen413

    (@ellen413)

    That’s strange. It should be there. Did you wait for the tests to complete? Make sure the “Results are still loading…” message is cleared at the top before checking.

    Just checked a third time. Opened all info drop downs – looked and searched “loopback” and there is nothing. Also copied to clipboard, pasted into document, searched. Nothing.

    I deleted the following plugins that are not in the amp ‘ecosystem’:
    Accelerated Mobile Pages (Addon mode)
    Rank Math
    Smush

    Still using:
    MC4WP: Mailchimp for WordPress
    Ultimate Blocks
    Updraft Plus
    W3 Total Cache
    — not in the ecosystem

    I have no idea if a plugin might be why I’m not seeing loopback requests in Site Health. I had to search what they are – but admittedly don’t really get why this is important. On one help forum, someone said a backup theme caused the issue (?).

    While my Site Health is ‘good’ – there is:
    “1 recommended improvement

    Themes add your site’s look and feel. It’s important to keep them up to date, to stay consistent with your brand and keep your site secure.

    Your site has 1 installed theme, and it is up to date.

    Your site does not have any default theme. Default themes are used by WordPress automatically if anything is wrong with your normal theme.”

    Could this possibly be the answer? I have not yet looked at how to name a default theme.

    Thank you for all of your time and help. I’m learning a lot, and hopefully this thread can serve others.

    Best regards,
    Ellen

    Thread Starter ellen413

    (@ellen413)

    It may actually be because you already had an amp directory when attempting to install the new AMP plugin build, so it created a new directory name upon upload. I’m not sure. You may need to fix the directory name using SFTP.

    This is important to do so that you get automatic updates properly.

    Got it. Thank you. The original 1.4 version was deactivated, not deleted, upon install. I deleted both versions, and reinstalled the plugin build and no longer have that message.

    Thread Starter ellen413

    (@ellen413)

    Wow, @westonruter! There are many new features to like with this amp build. I love it!

    Thread Starter ellen413

    (@ellen413)

    Learning something new every day…

    I have these two messages at the top:
    You appear to have installed the AMP plugin incorrectly. It is currently installed in the amp-1 directory, but it needs to be placed in a directory named amp. Please rename the directory. This is important for WordPress plugin auto-updates.
    The AMP plugin‘s post-processor cache was disabled due to the detection of highly-variable content. More details

    And this message further down:
    The post-processor cache was disabled due to detecting randomly generated content found on on this web page.
    Randomly generated content was detected on this web page. To avoid filling up the cache with unusable content, the AMP plugin’s post-processor cache was automatically disabled. Read more.

    I enabled the post-processor cache.
    I’m in Transitional mode.
    I tested the site with /?amp and there are 18 validation issues, all removable without visible consequence. This is what it was like before I switched themes from OceanWP to Zakra.

    I’m assuming the amp-1 directory is because it’s a not-for-release version? Is that what ‘alpha’ means?

    Thank you,
    Ellen

    Thread Starter ellen413

    (@ellen413)

    I don’t see the loopback requests in the Site Health Info. I opened all test areas and read through them all. Also searched “loopback” and there is nothing…?

    I’m using both AMP plugins to get a few more options on the look of the site, and ‘add on’ mode is supposedly compatible with the official AMP plugin.

    Thanks for explaining the alternative plugin replacement. I will follow instructions and see what happens. (I’m 13 hours ahead of NYC time, at the moment…)

    Thanks again for the attention and suggestions.
    Best regards,
    Ellen

    Thread Starter ellen413

    (@ellen413)

    Hello, @westonruter!

    Site Health = good. I don’t know what loopback requests are – I see nothing of that nature.

    The plugin is:
    AMP for WP – Accelerated Mobile Pages for WordPress
    Version 1.0.2 | By Ahmed Kaludi, Mohammed Kaludi | View details |

    The W# Total Cache was deactivated, but I still had the problem.

    I read through github, and have trouble understanding things.

    The 1.5.0-alpha plugin build you linked to: what do I do with that file once I download it? I’m afraid I’m not tech savvy and all I can do is try piece by piece and learn as I go. Do I need that plugin? Should I just ignore the message?

    Thanks,
    Ellen

    Hello,
    My site health is ‘good’ with only one recommendation for improvement, unrelated to AMP.

    I started fooling around with AMP several weeks ago. I had several errors, but they all could be removed without consequence. However, I decided to switch themes from one that was not listed on the ‘ecosystem’ (https://amp-wp.org/ecosystem/) – to one that was on the list. Right after the theme switch, I got a new message:

    URL validation failed to due to the absence of the expected JSON-containing AMP_VALIDATION HTML comment after </body>. This is often due to a PHP fatal error occurring. Please check your server PHP error logs; to do this you may need to enable WP_DEBUG_LOG. If you are stuck, please search the support forum for possible related topics, or otherwise start a new support topic including the error message, the URL to your site, and your active theme/plugins. Please include your Site Health Info.

    My active theme is Zakra. I switched from OceanWP.

    Active plugins:
    AMP
    Accelerated Mobile Pages (Addon mode)
    Site Kit by Google
    Akismet
    Share Buttons by AddThis
    Jetpack by WordPress
    MC4WP: Mailchimp for WordPress
    Rank Math SEO
    Smush
    Ultimate Blocks
    Updraft Plus

    *I disabled W3 Total Cache based on older support forum threads, but I don’t think that’s the problem.

    Then again, I don’t know what I’m doing. I read the php debug stuff and I started to get a headache.

    Thanks for any help/guidance you can give.
    Regards,
    Ellen

    Thread Starter ellen413

    (@ellen413)

    Bump. This issue is the number one problem slowing down my load speed, according to pingdom.

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