JohnnyJoomla

Yep still have issues with Bcc. Will contact Blueshost. Many Thanks!

Sorry for the late reply!

Tried your suggestion. It worked at first a couple times, but with more testing and other email combinations it stopped sending to non-domain name emails. Once domain named email addresses were used the form worked.

Thanks!

Thanks mbrsolution!

Not sure if this will show you much. I blured email addresses:

Well the above screen shot is probably not much of a help.
Basically I followed the instructions on this page: https://www.fastsecurecontactform.com/email-does-not-send

• This reply was modified 7 years, 3 months ago by JohnnyJoomla.

Not sure if the below is the error number. If not tell me where to find it. Thanks!

76632547: NO_SESSION

You have been redirected here from a site that is protected by GOTMLS Anti-Malware
———————————————————————————–
76633250: NO_SESSION

You have been redirected here from a site that is protected by GOTMLS Anti-Malware

Looks like the problem is from one hosting company… bluehost.com Here’s the server specs:
cPanel 2.2.31
Apache 2.2.31
PHP 5.6.29
MySQL 5.6.32
Perl 5.10.1

Upgraded to lastest plugin 4.16.49 on a godaddy site and all works fine. Here’s GD server specs:
PHP: 5.3.24
WordPress: 4.7.1
Plugin: 4.16.49

After you install it will mentioned the plugin isn’t “hooked” and need to install: https://www.ads-software.com/plugins/wp-autoloader/

Worked as it should on WP 4.4.2

Another vote for muliti-store location support. I need this yesterday!

Thanks for an awesome plug-in!

JohnnyJoomla

On the page were the gallery will be add:

[nggallery id=1]

“1” being the number of the gallery.

I think the best bet is to contact Genesis.

Awesome Links ESMI !

Thank You!

John

Also Robbie,

Take a look at the infected index.php code, you’ll see at the bottom some odd coding…it’s actually part of the eval hack coding and it’s encrypted too:

eval(base64_decode("JGNvZGUgPSAiICAgICAgICAgICAgICAgICAgICAgICAgICA
gICAgICA....AiIiwgJGNvZGUpOw=="));

Looks like the hack doesn’t change anything other than the index.php files. I hope!

As mentioned don’t just delete the eval hack code… use a fresh “index.php” from a new download of WordPress.

Take a look at the infected index.php code, you’ll see at the bottom some odd coding…it’s actually part of the eaval hack coding and it’s encrypted too:

eval(base64_decode("JGNvZGUgPSAiICAgICAgICAgICAgICAgICAgICAgICAgICA
gICAgICA....AiIiwgJGNvZGUpOw=="));

Looks like the hack doesn’t change anything other than the index.php files. I hope!

CarR,

Have you checked the “index.php” for a hack on the root directroy as 1.8.0 had a hack.

Don’t know if this will help you… this was posted by me in a different thread:

The same happend to me yesterday…. unfortunately the install disabled all my database driven sites, Joomla and WordPress, on my shared server. Yesterday’s 1.8 had an “eval” hack in it and modified/rewritten all the “index.php” files in each sites’ root directory.

Easy solution is to download a fresh install of WordPress to your computer and replace the infected “index.php” file in the root directly with the newely downloaded “index.php” file.

It’s not enough to delete the “eval” code in the index.php file.. as other parts of the php code could have been subtly changed.

In my case I did the same for my Joomla sites also.

Wish the developer was more forth coming in about this hack!

Robbie,

Have you checked the “index.php” for a hack on the root directroy as 1.8.0 had a hack.

Don’t know if this will help you… this was posted by me in a different thread:

The same happend to me yesterday…. unfortunately the install disabled all my database driven sites, Joomla and WordPress, on my shared server. Yesterday’s 1.8 had an “eval” hack in it and modified/rewritten all the “index.php” files in each sites’ root directory.

Easy solution is to download a fresh install of WordPress to your computer and replace the infected “index.php” file in the root directly with the newely downloaded “index.php” file.

It’s not enough to delete the “eval” code in the index.php file.. as other parts of the php code could have been subtly changed.

In my case I did the same for my Joomla sites also.

Wish the developer was more forth coming in about this hack!

Once you take a look at the infected index.php code you’ll see at the bottom some odd coding…it’s actually part of the hack coding and it’s encrypted too!:

eval(base64_decode("JGNvZGUgPSAiICAgICAgICAgICAgICAgICAgICAgICAgICA
gICAgICA....AiIiwgJGNvZGUpOw=="));

Looks like the hack doesn’t change anything other than the index.php files. I hope!