Shortcode Issues URGENT

Support
#1

Hi there,

I’m trying to add a Super Forms shortcode by using the classic RAW content element, but it’s only showing the code on the page, not the form we’ve built.

The code used is [super_form id=“325”] and this can be seen at www.viewbyvideo.tv/book

Is there a way to fix this? I have clients waiting to use this form in the morning.

Thanks!

#2

Hello @viewbyvideo,

Thanks for asking. :slight_smile:

Can you please confirm that Super Form plugin is installed and that it’s activated? I checked the website URL you have shared and as of now 4 plugins are in active state and Super Forms is not in that list.

Please make sure Super Form plugin is install and is activate to output the forms on front end.

Thanks.

#3

Hi there,

Yes, it’s installed and activated, otherwise I wouldn’t be able to create the form and generate a shortcode.

#4

Hello @viewbyvideo,

Thanks for updating the thread. :slight_smile:

Okay, can you please try testing for plugin conflict? Please deactivate all the plugins and see if form displays on the front end. If it does then there is a plugin that causing conflict. After that try activating one plugin at a time to narrow down.

If above solution does not work, would you mind sharing website login details (username, password) in a secure note for us to take a closer look?

Please note that Super Forms is a 3rd party plugin and supporting 3rd party extension falls outside the scope of support we can offer as we have limited control on the functioning of a plugin. However, I can take a closer look and if there is something minor that’s causing the problem, we can definitely share the solution with you.

Thanks.

#5

Thanks for replying.

I’ve deactivated all plugins and it’s made no difference, so I’m certainly baffled!

I’ll send you a note with some login information ASAP.

Thanks!

#6

Hello @viewbyvideo,

Thanks for sharing the details. :slight_smile:

Form is showing up absolutely fine on my end. Please see screenshot.

Please note that you won’t see the preview in the builder. Bellow are the steps I took:

  • I first wanted to see wether or not form shows up on the front end. To do that I created a new page and used WordPress editor to add the form shortcode. Then I previewed the changes and form was showing up on front end.
  • After that I edited the page in Cornerstone and under Raw Content element I added the shortcode and in that also form is working fine.

Here is a screencast that I have recorded. Please take a look. https://cloudup.com/czGARDY_eOC

Thanks.

#7

Thanks for the info. I have found a glitch which is why we’re seeing conflicting information:

If you create a page with the default page template, the form works. If you create a page with Blank-Container, Header & Footer the shortcode does not work.

So it looks like that’s where the problem is. How can we go about getting this fixed?

I created this new page as an example:

http://www.viewbyvideo.tv/booking/

#8

Hello There,

It seems that you are having an issue with the shortcode of the 3rd party plugin. I have edited both of the pages and added this:

[super_form id="325"]

[recent_posts count="4"]

Only the recent post shortcode is rendered. There could be a problem with this plugin which we do not have any idea. I would highly recommend that you contact the creators of the 3rd party plugin SuperForm. This could be a bug in their plugin and they might need to know to further investigate with this issue.

Thank you for you understanding.

#9

OK, I’ll get in touch with them and let you know what they say. I believe they’ll say that the issue is with the theme, not the plugin, but we’ll see.

#10

Hi @viewbyvideo,

Let us know how it goes.

Again, we cannot provide support for third party plugins or scripts as our support policy in the sidebar states due to the fact that there is simply no way to account for all of the potential variables at play when using another developer’s plugin or script. Because of this, any questions you have regarding setup, integration, or troubleshooting any piece of functionality that is not native to X will need to be directed to the original developer.

Thank you for your understanding.

#11

Hi @nico

Yes, I understand completely. I hope the developer does!

#12

Thanks for understanding :slight_smile:

#13

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.