MrsJessicaSimpson

Hi chaps and chapettes, ..

Most excellent plug-in that gives users a better onsite experience, but I’m also being caught up in the force update after a WordPress post has been updated, and the lack there off of any audio output thereafter.

Bulk update being disabled is a bit of a pain; that I am also requesting to be enabled asap, or at least an update button per post? – That would be good.

This is not a request for assistance, but more like an acknowledgement of an issue. A running known issue that appears to be affecting quite a few of us with it’s strange effect.

Keep the faith, ..

One of my biggest concerns and worries in using the AWS Polly Plugin, is just how much this is gonna cost me once I’m out of my free period.

toshiamcbrowns (@toshiamcbrowns), I’d surely like to know how your users managed to run up a bill like that.

Now, author of plugin: don’t get me wrong, this is a wonderful piece of code that really does add value to any web-site, but this cost thing bothers me greatly, and then I see this: a bill for $55, and for only one month, .. gasp!

Would like to know the outcome, Laters ..

HeHeHeHe, .. mustn’t smile.

Contacted you chaps on Twitter, and @podsframework sorted it out.

It seems that:-

‘Looks like one of our plugins we had activated “GitHub Updater” was experiencing some major slow downs. We deactivated it and the site is now running like normal again. Sorry about that!’

Happy daze, as I say: you can delete this message is you want, it doesn’t detract from your most excellent plugin that I’ve now subscribe to.

All the best, ..

From my observations only, and please take not that I’m not the plugin admin. The text below is cut from one of my reviews.

‘.. the Plug-in needs to be reactivated on the settings page:-

Text To Speech – Amazon Polly
Amazon Polly configuration
Source language: [ English ]
Enable text-to-speech support: [ ] <– this becomes unchecked, rechecking it again and it’s all working as it was. ..’

It comes from a situation where your internet fails (locally), the box also needs checking to start exploring the wonderful world of Amazon voices.
In fact: illogically, most pages of the plugin features need activating.

Hope it helps, .. Jessica.

I’ve been following this problem with intense interest, and I’ve also seen something about this issue *somewhere* on the web in the last year: somewhere being the key word here, (I know about it because I’m coding my own theme for fun.)

The link below isn’t the one I read in depth, and I actually think that it was on the WordPress site itself, but it does go into depth about the problem being described.

https://wordpress.stackexchange.com/questions/209693/wordpress-page-2-404-pagination-problem-what-to-do

The key info I’ve taken from this is — [Flush the database Cache].
In the back of my mind I also remember someone suggesting on the WordPress site that re-activating an official theme will do just that

Plan of attack .. find the theme “twenty — (the lowest you can find)”, 2011 is good, and then reactivate it. Been there, done that; and I have to admit that the entire process is quite painful; especially in resetting your menus, but at the same time the theme also resets the databases links. Run 2011 for a short while to resettle your database in place whilst also checking that the pagination is working.
– If it is, then reinstall a clean version of ‘Author’ again.

All of the above might not work, (and I’ve never had this particular problem), but it does exist out there in the WordPress community.

Hope it helps, ..

I’m also having this issue, but I also see from your link that you’ve sorted it out.

The read-more button you have installed looks quite good, what did you do?

Hope you can help ..

Hi Umit Ozaydin (@umitdragoman),

If this system did a (thumbs up) – then you’d get one.

Many thanks, ..

Additional:

I’ve got error reporting enabled on my 404 page, and this email was sent to me, and yet again I must add: it’s a local server that I’m working on, so the link below won’t work.

[eMail report begins.]
A user tried to go to $website/wp-content/plugins/expand-maker/css/colorbox/colorbox.css?ver=5.2.4 and received a 404 (page not found) error.It wasn’t their fault, so try fixing it, they came from .. https://writeon.test/wp-admin/admin.php?page=readMore
[eMail report ends.]

It may help you to identify the fault: that appears to (lie) within a rouge-one CSS file.

Sorry about that lying thing, .. keep the faith: and may the Force be with you.

Hi Chaps ..

Just installed the plugin, and haven’t even inserted any read-more tags yet, but this came up: so I started searching the Forums for a solution. BTW: I’m working locally on the Laragon server, (so revealing the paths shouldn’t be a security issue), everything else is working fine here, but the plugin certainly isn’t playing ball.

By-the-by — the Plugin itself looks absolutely perfect for my needs, but I’ll disable it till this minor issue is sorted out.

[Warnings report begins.]

Warning: Use of undefined constant YCD_TEXT_DOMAIN – assumed ‘YCD_TEXT_DOMAIN’ (this will throw an Error in a future version of PHP) in C:\laragon\www\writeOn\wp-content\plugins\expand-maker\classes\ReadMoreData.php on line 237

Warning: Use of undefined constant YCD_TEXT_DOMAIN – assumed ‘YCD_TEXT_DOMAIN’ (this will throw an Error in a future version of PHP) in C:\laragon\www\writeOn\wp-content\plugins\expand-maker\classes\ReadMoreData.php on line 238

Warning: Use of undefined constant YCD_TEXT_DOMAIN – assumed ‘YCD_TEXT_DOMAIN’ (this will throw an Error in a future version of PHP) in C:\laragon\www\writeOn\wp-content\plugins\expand-maker\classes\ReadMoreData.php on line 239

Warning: Use of undefined constant YCD_TEXT_DOMAIN – assumed ‘YCD_TEXT_DOMAIN’ (this will throw an Error in a future version of PHP) in C:\laragon\www\writeOn\wp-content\plugins\expand-maker\classes\ReadMoreData.php on line 240

[Warnings report finished.]

Hope it helps – Jessica.

Podcast? – No idea, .. what’s wrong with yours?

The set up at this end seems fine, but that said: I’m not keen on iTunes to do anything right.

My twopence worth, .. for what’s it’s worth.

Same as the above, but I’m working locally on a test rig developing a theme.

I’ve edited the PHP.INI file to include the ‘extension=php_openssl.dll’ aspect, and that at least has enabled ‘WP MAIL SMPT’ to send test messages, but as yet: the WordPress core system itself won’t send me these emails .. really frustrating.

Been searching Google, and this weird issue appears to be common: with most users simply either ignoring it, or using the http/(your site url)/wp-admin/options.php method to force the change through.

BTW: Horrified by what’s actually in the options screen. And yes: I could possibly change the admin email there, but even on a test site: (with backups), I really don’t want to touch that aspect of my installation.

Been scratching my head over this for a week now, and I’m no closer to finding a cure; other than suggesting that it’s a hosting issue, but there again: I can’t find what’s stopping the emails being sent in my Apache config file.

Hope someone with better detection skills can point us in the right direction, cos this useless detecting detective has drawn a blank.

Rgds – Jessica.

If you could up-vote a message thread here, then I would, ..
Thank-you so much for sharing.

I’m also on CF7 Version 5.1.3

– And what’s being reported here is really weird ..

I’m using a browser called SlimJet – which is a Chrome fork: sort of.
I don’t use Chrome because of its slow loading time, but using it on my own site I get this error with an orange border ..

There was an error trying to send your message. Please try again later.

It occurs in the Registration page and Boxzilla Popup, the side widget works as it should with Chrome, and all three forms work fine under SlimJet.

The error is fascinating ..

On Chrome: the inspected elements are as follows ..

<p><input type=”submit” value=”Register” class=”wpcf7-form-control wpcf7-submit”><span class=”ajax-loader”></span></p>

<div class=”wpcf7-response-output wpcf7-display-none wpcf7-spam-blocked” style=”display: block;” role=”alert”>There was an error trying to send your message. Please try again later.</div>

On SlimJet it says ..

<div class=”wpcf7-response-output wpcf7-display-none wpcf7-mail-sent-ok” style=”display: block;” role=”alert”>Thank you for your message. It has been sent.</div>

https:\\www.b92.co.uk to see it in action, but the link is irrelevant.
– I wonder what’s happening here?
Hope my input helps track the strange condition down.

Googled it, and some interesting reading popped up: you may like to look at this one below as a starter.

https://www.ads-software.com/support/topic/notice-wpcf7_remove_shortcode-is-deprecated/

The general consensus from a quick scan, is that it may well be another mailer plugin that’s causing it, and not CF& at all.

As I say, it may or may not help you.

marco3253 (@marco3253)

I just send you a ‘testing testing times’ from your form, and I saw a mail sent success message as well.

If you got it: then I guess its working again, ..