smartyp

Nothing appeared to go wrong on the update – I only noticed when a backup failed to run. I went to check the job, and noticed the S3 secret key field was now showing empty. The access key was still there. I re-entered the secret key and the backup completed.

This happened on more than 1 site (which were working before the update) so I thought it was a wider problem.

Now checking the log for the job that originally failed I can see:
“ERROR: S3 Service API: Error retrieving credentials from the instance profile metadata server”

Hope that helps.

I don’t use MAMP, but in the docs under ‘First Steps’ it says “you must enter the Apache port at the end of the URL, e.g.: https://localhost:8888” – do you get server not found if you enter that URL? If so, it’s worth trying a different web browser (Chrome/Firefox).

It’s working now – I can see WordPress at that domain.

When you update name servers it can take some time for that change to be seen everywhere (propogate).

The only relevant setting is “Show comments cookies opt-in checkbox.”

To get ‘Your comment is awaiting moderation’ now, you have to turn that setting on. This will then add a checkbox to the comment form itself that says “Save my name, email and website in this browser for the next time I comment”. If the commenter doesn’t check that box they won’t get a confirmation message (because there is no comment cookie written, which is what is being used to trigger the message).

I agree it sounds strange – as a design decision it makes no sense to me ??

This isn’t a problem with the database or WordPress.

“Safari can’t find the server” means the web server, i.e. the Apache part of MAMP, isn’t reachable.

Have you clicked on the Start Servers button in MAMP? And do they show as ‘green lights’ in the top right of MAMP?

Um, it didn’t work, but you rated it 5 stars..?

Does it work if you untick the Regex box (as you don’t appear to be using regular expressions for this redirect)? Or are there any rules before this one that might be overriding it (this one is position no.4)?

Your demo period does not work – the charge goes through immediately. I contacted you about this but got no reply.

… and still no reply of any kind anywhere…

@feedsapi Unfortunately I can understand this reviewers frustration. As a paying customer I’ve been trying to get any kind of response from your support since 15th June. I’ve sent 6 emails since then plus a chat ticket detailing the problems I’m experiencing – but haven’t had any reply at all. I’ve tried all the different emails listed on your site, plus the one you gave out above.

I don’t know, maybe you have an email problem? But then it looks like you’ve stopped responding to support threads about 6 weeks ago too, so I’m not really sure what to think?

Use the Customizer for this, i.e. Appearance/Customize. Then select the Site Identity section, and just untick the box that says ‘Display Site Title and Tagline’.

Whilst it would be nice to have a theme setting for this, you can just use the <!–more–> tag as @shariqkhan2012 originally suggested (there is a button for it in the visual editor). I have tested that this does work.

It will then cut-off the post at the point you specify for your categories, homepage, tag pages etc.

It may or may not be directly related to this problem, but I’m seeing a whole bunch of entries in the wp_options table with option_name like ‘_transient_timeout_rss_%’, ‘_transient_rss_%’, ‘_transient_timeout_feed_%’, ‘_transient_feed_%’.

I may be having the same issue as you (also with a premium key). The plugin will run on schedule over and over again without importing anything when I can see there are posts waiting to be imported. I’ve then manually run the ‘save and import’ repeatedly with 0 imported, then it suddenly works without anything having changed. Maybe the API is failing or timing out?

Yes, there is definitely an issue with saving settings.

I’ve experienced it blanking the feed settings twice now on a live site (v2.5.2). This was whilst doing a ‘save and import’ to manually run a feed that was already set up (no edits to the feed at all). It doesn’t happen every time and I can’t pin down exactly what causes it but there is definitely a bug here.