‘Field name’ – shortcode stopped working

Hi Frank,

The fact that sometimes the brackets get stripped on save does definitely seem like a conflict. Is there some kind of page builder or visual composer included with this theme? As a test, could you create a new page and disable the page builder for that page, so that it’s just the regular WordPress editor? Then try putting in your shortcode. Does it then display properly on the front end?

Hi there,

Sorry for my late reply! Yes, the theme came with Visual Composer. I did as you instructed and the shortcode displays correctly on the front end!

I’m not quite sure what this means though, since the original page I’m trying to use the shortcode in, doesn’t have the Visual Composer turned on. Does it mean that a page shouldn’t have been CREATED with use of the Visual Composer, because later on it doesn’t matter if the Visual Composer is turned on or not?

Basically, my question now is, what do I do to get the original page containing the shortcode, to work again? And can I use the Visual Composer at all (since it is handy to use after all)?

Thanks so much for your help, I almost started thinking I spent money on a theme that’s incompatible with the Front End Only Users plugin.

Looking forward to your reply!

KR,
Frank.

Hi Frank,

You should be able to use Visual Composer. We just wanted to test it. Perhaps there is a specific element or feature in Visual Composer that causes the conflict. Or perhaps it is the combination of theme/plugin/visual composer that might trigger the conflict.

You say that Visual Composer is disabled for the page that isn’t working. In that case, is the [user-data] shortcode the only shortcode on that page? What other page content is there?

Hi there again,

The [user-data] shortcode is the only one I put in there. The page however is one that came with the theme and since I like the features and look of this page, I’m trying to adjust the content to my liking. There might be other shortcodes in there, although I’m not quite sure when something qualifies as shortcode: is anything between [brackets] a shortcode? If so, I identified some, seemingly corresponding with the Revolution Slider in the theme, looking like this:

data-x=”[‘center’,’center’,’center’,’center’]” data-hoffset=”[‘0′,’0′,’0′,’0’]”
data-y=”[‘middle’,’middle’,’middle’,’middle’]” data-voffset=”[’30’,’29’,’37’,’40’]”
data-fontsize=”[’65’,’55’,’40’,’25’]”

Should you wish to see the entire code, the demo version of the page I’m using is the following: https://rnbtheme.com/twenty_ninth/

Again, thanks so much for helping out!

KR,
Frank

Hi Frank,

All of that is in the regular WordPress WYSIWYG editor on the page edit screen? Where did it all come from? Was it when you switched off the Visual Composer, it left all those shortcodes behind?

All it would take would be one missing quote or bracket and it could mess up the rest of the code.

What happens if you put the [user-data] shortcode before all other content on that page? Does it render?

Hi there,

The code I copy/pasted in my previous message, I copied from the source page of the demo page.

I just checked the regular WP editor screen and it seems that basically all the code is surrounded by ‘[ ]’ brackets. (by the way, there’s hardly any difference in switching between Text and WYSIWYG mode: both are the same bunch of code and brackets). To give you an example, here are the first lines of code from out of the WYSIWYG editor:

[vc_row dfd_row_config=”full_width_content”][vc_column][rev_slider_vc alias=”Mainslider_28″][/vc_column][/vc_row][vc_row force_equal_height_columns=”main_row” dfd_row_config=”full_width_content”][vc_column column_bg_check=”column-background-dark” width=”1/2″ css=”.vc_custom_1440230876157{background-image: url(https://www.fjvanbeek.nl/wp-content/uploads/street.jpg?id=11518) !important;background-position: center !important;background-repeat: no-repeat !important;background-size: cover !important;}”][ultimate_spacer height=”180″ height_on_tabs=”100″ height_on_mob=”430″][ultimate_heading heading_type=”customizable” heading_tag=”h4″ heading_content=”Specialistische
Allrounder” main_heading_default_weight=”500″ main_heading_font_size=”100″][/ultimate_heading][ultimate_spacer height=”180″ height_on_tabs=”100″ height_on_mob=”430″][/vc_column][vc_column width=”1/2″ css=”.vc_custom_1440144493108{border-top-width: 30px !important;border-right-width: 30px !important;border-bottom-width: 30px !important;border-left-width: 30px !important;background-color: #ffffff !important;border-left-color: #ffffff !important;border-left-style: solid !important;border-right-color: #ffffff !important;border-right-style: solid !important;border-top-color: #ffffff !important;border-top-style: solid !important;border-bottom-color: #ffffff !important;border-bottom-style: solid !important;}”][vc_row_inner css=”.vc_custom_1440151738595{border-top-width: 1px !important;border-right-width: 1px

I tried to put the [user-data] first (I put it right before and right after the slider) and this does work: the data is displayed correctly.

Strangely enough, when I switch back to the Visual Composer, the text + [user-data] shortcode I put in is nowhere to be found? But when I switch back to the WP editor, it’s right there?

At least I’m glad to see that putting the [user-data] shortcode first works, so there must be some sort of hickup somewhere?

Much appreciating your help!!

KR,
Frank

If the shortcode works when you place it at the top, then that indicates that the shortcode is functioning correctly.

With that many shortcodes on the page, it’s definitely possible that there could be a missing quote or bracket that could mess it up. You’d have to look through to find this.

You could try enabling the Visual Composer again and adding our shortcode to a new text block, to see if that works.

Hi there,

I went through the code but didn’t manage to find a missing bracket or quote. I haven’t tried your suggestion yet for adding the shortcode to a new text block, but I did discover something else:

if I put the shortcode somewhere between ‘regular’ text (that is, no heading or whatsoever), the shortcode works, but when I want to use the shortcode in a heading of some kind, things go wrong. See below for an example of the heading code with the shortcode inserted:

[ultimate_heading heading_type=”customizable” heading_tag=”h4″ heading_content=”Waarom [user-data field_name=’Bedrijfsnaam’]?” main_heading_default_weight=”500″ main_heading_font_size=”100″][/ultimate_heading]

What strikes me, is the forward slash at the end: isn’t the forward slash used only in combination with the ”<” symbol?

Also as a test, in the code above, I replaced all brackets with ”<” and ”>”. As a result, the heading fails to show properly and at the front end, the entire code shows, but this time the shortcode does work?

As it seems to me now, the shortcode has a conflict with the code that creates the heading font.

I hope I’m explaining this clear to you and that I’m on to something. Any ideas on the above?

Again, thanks so much for the support!!

KR,
Frank.

Hi Frank,

The slash can be used in a closing shortcode tag. That’s normal.

You’re trying to use a shortcode within the attribute of another shortcode. That won’t work.

Hi there,

I reported back to support at the WP-theme, and they pointed out a text block module that doesn’t conflict with the shortcode, and it seems to be working, so I guess there’s no problem anymore.

Thanks again for helping me out and searching along for the exact problem!!

Much appreciated!

KR,
Frank