mrioa

how do we ping them? or is that hashtag enough?

@drew75 “which would leave one to believe that replying would be going to the admin email ([email protected])”

no, it should not ?? the “reply-to” is a hidden field, they won’t see it in the body of the email, so that quote is useless. the form email notification has to be sent FROM the admin email (or at least from its same domain). it can’t be the users submitted email because your server might not be allowed to send emails in the name of that user.
that is where the REPLY-TO configuration i mentioned comes in handy. so when your client directly replies to the email, the email client (outlook, gmail, …) will use the REPLY-TO address as the recipients email address.

• This reply was modified 1 year, 1 month ago by mrioa.

that should be working already as you have {field.email} in your REPLY TO setting. so if someone gets the notification in their inbox, when they hit the reply-button, it should have the contacts email as its target, not the admin email.

you could change the “from” email via enabling the “dev mode” in the general ninja forms settings page. then you will get “advanced settings” at the bottom of your screenshot to change “from name” and “from email”.

BUT beware that this would most likely result in the notification not being delivered (spam alert), because you usually don’t have to right to send as that users email.

if i remember it correctly it’s right there: /ninja-forms/assets/js/min/front-end.js

but it is a minified file, so not too easy to edit.

thanks, this solution helped!

all my websites using the latest ninja forms 3.6.30 are affected by this issue. rolling out your temp fix as i type this…

i also contacted the NF support and linked them to your post – thanks again for sharing your solution.

I also had the same problem on my local development system today after updating to Apache 2.4.26.
There’s already a bug report for it.

A quick fix, if you don’t have access to your webserver config, is to add a line in your .htaccess file:

ProxyFCGIBackendType GENERIC

According to the Apache 2.4.26 changelog they changed this setting to FPM and created this new setting to let server admins change it back to the old GENERIC value.

Hi me-boater,

same problem here – thanks for the hint towards the child-theme, I’ll have a look at it now ??

Cheers,
mrioa

/edit
Ok I just checked – same problem having my parent theme activated. So in my case its not the child-theme.

Hi Mike,

I used to see a “WP_Error” too. But it wasn’t shown in the Plugin-Page but in my database where the information about the wp-cycle-images are stored.

Just curious if you set the Image Dimension (width) to less than 101px?

(More info about my problem can be found in this topic )

Bye,
Mario

Hi dgreco,

I’m experiencing the exact same problem.

Before uploading (and making your settings dissapear), have you changed the width of the image rotator to 100px or less?
I just found out that it has to be at least 101px wide to work properly.

After some diggin in the database, I found this little workaround that worked for me. Maybe I find a better way after the weekend though.

If you have access to your wordpress database, execute the following SQL statement (At your own risk and only if you know what you’re doing. A backup wouldn’t hurt here too!):

UPDATE wp_options
SET option_value = ''
WHERE option_name = 'wp_cycle_images'

Info:
When the width is set to 101 or less, there is an Error Message stored into that database field and it can’t get parsed by the plugin anymore.

The above statement sets the wp_cycle_images option to empty. Now the plugin settings are shown again and you can set the width to a higher value.

Bye,
Mario

Hi xa2,

I’m not sure if this is what you’re looking for:

SELECT option_value
FROM  wp_options
WHERE option_name =  'wp_cycle_images'

shows the array of your cycle-images (not easy readable though). Exchange wp_cycle_images with wp_cycle_settings to find the settings.

Mario

i’ve created an archive-page where i use the following code to display the past events:

<?php
if (class_exists('EM_Events'))
{
echo EM_Events::output( array('limit'=>20,'orderby'=>'start_date','order'=>'DESC','scope'=>'past','pagination'=>1));
}
?>

but the pagination isn’t working (for me) so i’m not using it right now (without limit and pagination 0)

hth.