ambitiouslyalexa

Hi Steven,

I am not exactly sure where or how i would go about editing the line you’re referring to, but I just sent the support email some login credentials to investigate this further!

Because I think the exact same thing, that having a sudden incompatibility with the theme, as my host claims, does not make sense if the theme was functioning just fine for so long.

I know I use several plugins on top of the theme to customize things like my homepage beyond the theme’s default, and I wonder if that might be a recipe for disaster waiting to happen!

Oh really it’s up and viewable?! That’s so interesting! Even in incognito mode, it is down for me. But I’m happy to hear that at the very least. Thanks for your prompt response!

Here is the error log my host sent me. The host is NameHero:

log:

[03-Apr-2023 11:52:58 UTC] PHP Warning:  Use of undefined constant WPLANG – assumed ‘WPLANG’ (this will throw an Error in a future version of PHP) in /home9/ambitiou/public_html/wp-content/plugins/wp-resized-image-quality/wp-resized-image-quality.php on line 88

[04-Apr-2023 01:30:58 UTC] PHP Fatal error:  require(): Failed opening required ‘/home9/ambitiou/public_html/wp-content/themes//inc/back-compatibility.php’ (include_path=’/home9/ambitiou/public_html/wp-content/plugins/kirki/:/home9/ambitiou/public_html/wp-content/plugins/kirki/core:.:/opt/alt/php74/usr/share/pear’) in /home9/ambitiou/public_html/wp-content/themes/elara/functions.php on line 13

That worked perfect! Thank you!

Hello,

Yeah, I’m still not going to upgrade if I have to risk functionality issues on my site. Maybe you fixed something in the latest upgrade, but who knows if the next one will break once again.

So in case you wonder what I’m doing, I am safely keeping my plug-in on the older version that I know will be stable/work.

Yay, that worked! Thank you! Is there a reason why it’s frowned upon?

Is there a code for changing the font size of lists even when they are explicitly set in editor? I have several posts with lists manually set to 18px in the past, so was wondering if I could override those!

That worked, thank you! You never fail me!

I just went through that and all of my settings were already filled out exactly like that document says to do. It’s gotta be something else.

I looked at the documentation and I don’t have the option to do what it’s saying.

Under my form builder, I went to field options > advanced options and I do not see “whitelisted domains.” I only have placeholder text, default value, and CSS classes. I made sure my plugin was updated to the latest version and still, nothing.

That worked, thank you!

That worked, thank you!

I gave that a try and it’s been working perfectly all day with about 10 new subscribers being successfully subscribed! Thank you so much, that’s a big help!

I should also add that it looks like not every contact is failing to be subscribed–I just looked at my most recent subscriber and they were successful. But there is still a vast majority of contacts that aren’t being subscribed, even when they submit both their firstname and email. So I’m not sure what the discrepancy is there.

Hi Adam,

Here is a link to the exported pop up: https://drive.google.com/file/d/1DRFrbrEQibjH9W-Gnz2-VhmVunQZp0PJ/view?usp=sharing

I do see the emails stored in the local list, but when I export the spreadsheet, it doesn’t show in the spreadsheet which contacts have been successfully added and which haven’t, so it looks like it’ll be a pretty manual process of looking into which contacts were successful and which weren’t.

I have the firstname and email fields set to required on the popup, and always have. It looks like many of the submissions provided both their first name and email, too. So I believe the error is a false one, maybe a glitch? I even tried the popup form myself by entering a new email and my name, and it shows “success” on the front end, but shows that it failed on the back end and does not transfer to Mailchimp.

Wow, you’re right! I just deactivated my WP-Optimize plugin and that fixed the issue. I didn’t find a “no conflict” option though, so I think I might just have to go without it and see if it impacts the performance.