etellewyn

I am doing this exact thing but in the live page, all I get is the actual literal shortcode being spit out.

I have:
<div class="newsletter">Get Updates and the Free Guide! <?php echo do_shortcode('[mc4wp-form]'); ?></div>

On the live page I get (html source)
<div class="newsletter">Get Updates and the Free Guide! [mc4wp-form]</div>

[Please post code & markup between backticks or use the code button. Your posted code may now have been permanently damaged by the forum’s parser.]

?!?!?

Any ideas??

Just left a reply in gravity forms forum about this issue. According to GF admin, the curCSS script (which is the source of this issue) is no longer required by Gravity Forms and will be removed from the code in version 1.7 when it’s released.

I can confirm that the conflict is still present with AMTPV version 2.6, GF 1.6.11 and WP 3.5.

Love both plugins and look forward to a resolution.

Update for anyone that is interested — Though I never did find an answer to my “unexpected token” issue, I did find a solution — I switched hosts! This site had been hosted on Godaddy, I’ve been bugging them to switch for some time and they finally agreed — and Bingo, the plugin worked again!

Both hosts have the same version of php and mysql but doing phpinfo() on both hosts indicated that Godaddy had a bunch of stuff turned off that Bluehost had turned on. I have no idea which setting might have been causing the fault, but I am concluding that must be it. Maybe something worth pursuing (by somebody who knows more about this stuff than me)

I hope this is helpful to somebody. Would be great for the developer to weigh in.

@tannermirabel THANK YOU! This was exactly what I needed. Totally fixed the problem!

Thanks a lot for taking the time to post this!

most sincerely,
-barbara-

I am attempting to fix this same error — Can you please give the full text of the lines of code I am looking for? The lines are coming over double-spaced so I’m not sure if I am looking at the same lines that you are. (For example, there is nothing at line 1028 in my file)

Would really appreciate a hand, thanks!
-barbara-

My bad. It was set at a default of 600 somehow. (palm-to-head) This solved it. Thanks!

Hey all, I tried something that I found on another site, and it solved the issue for me. Try this to see if it helps for yours:

Look for this in wpaudio.min.js —
{jQuery(‘a[href$=.mp3]’).addClass(‘wpaudio’);}

and change it to this:
{jQuery(‘a[href$=”.mp3″]’).addClass(‘wpaudio’);}

(note the quotation marks on the second one)

Here is where I found the tip https://www.ads-software.com/support/topic/no-mp3-play-button-just-a-link?replies=41#post-2201546

Oh so this is the reason it doesn’t work? Makes sense. I have tried everything I can think of. Just get a link, no player.

PLEASE UPDATE ASAP!

actually never mind I figured it out. Your calendar embed code needs to contain the width=”xxx” and height=”yyy”. This should solve the problem.

I am having the same problem. Did not even configure any colors. Just added calendar *and* set the width.

@franworks, you just saved me a ton of time! THANK YOU for this tip! is now working.
Thanks!

Gayatriom: no the 4G hosting is not dedicated, it’s still shared. I don’t know the technical details about the actual configuration except that it’s spread across multiple servers so that when one is slow or goes down, it does not impact the performance.

MMMemories: This sounds like a problem with your theme. I would go in via FTP and manually remove that theme from your wp-content/themes folder. As I said, in our case the 500 errors happened from two causes: One was intermittent due to slow server (fixed by switching hosting package), and the other was more serious, due to an .htaccess misconfiguration. You seem to have a more serious type!

Good luck to you!

In our case the 500 error was only intermittent and was occurring along with slloooowwww speeds. So we upgraded to their “4G” hosting which made it worse at first but then completely solved the problem.

We have since ended up with two conclusions regarding this error…
1) in our case it was at least in part related to bandwidth, and 2) it is also related to the .htaccess file.

When we first moved to the 4G host, everything broke completely with a 500 error and this was due to the .htaccess file. It seems that their 4G host doesn’t handle these the same as their shared hosting server does. I know almost nothing about .htaccess so I don’t know what the offending command was, but removing the .htaccess file completely resolved the issue (and of course resulted in other file not found issues! so if you know how to read/write .htaccess you’ll have a better time navigating this than we did)

2) since moving to the 4G hosting, WordPress is LIGHTNING FAST and the 500 errors have stopped. I have seriously never had it respond this fast (even in admin) on any other host. it’s amazing. To be honest I was secretly hoping to move to a different host because I don’t like Godaddy as a company, but this 4G/grid hosting thing is now faster than any other host I currently work with so I am going to stay at least until I find another that is as fast!

I’m coming in pretty late to the game but just found this thread today and wanted chime in to say that I am also having this issue with Godaddy. I have a couple different (unrelated) client sites and all have intermittent 500 server error problems on godaddy. (interestingly they usually have them at the same time, this is why I am sure it’s their problem) I don’t do anything to cause it and it also resolves by itself (until next time).