[url] not working

I guess I should have realized the links would not show correctly in my original post I will try with code format here or removing the <, which is actually in my code.

<a href="[url logout go='home']">Logout</a>
<a href="[url site]">Site</a>

a href=”[url logout go=’home’]”>Logout/a>
a href=”[url site]”>Site/a>

I tested these and they’re all displaying the correct URLs. Do you mean that the following displays nothing?

[url site]<br>
[url login]<br>
[url logout go="home"]

I wonder what is different in your situation.. Maybe something is surrounding all of these that is affecting the output?

Version 1.7.5 and WP 4.1.

I am not specifically adding anything before or after the code. Again, here is the entire content of the page I am testing.

<a href="[url logout go='home']">Logout</a>

[url logout go='home']

[url logout]

[url]

<a href="[url site]">Site</a>

[url site]<br>
[url login]<br>
[url logout go=&quot;home&quot;]

test

And here is the source code I see when I visit the web page.

<a href="https://mywebsite.wpengine.com/logout/" title="Logout"></a><div class="entry-content"><p><a href=”<a class="d4pbbc-url" target="_blank" href="ogout"></a>“>Logout</a></p>
<a class="d4pbbc-url" target="_blank" href="ogout"></a>
<a class="d4pbbc-url" target="_blank" href="ogout"></a>
<a class="d4pbbc-url" target="_blank"></a>
<p><a href=”<a class="d4pbbc-url" target="_blank" href="ite"></a>“>Site</a></p>
<p><a class="d4pbbc-url" target="_blank" href="ite"></a><br><br />
<a class="d4pbbc-url" target="_blank" href="ogin"></a><br><br />
<a class="d4pbbc-url" target="_blank" href="ogout"></a></p>
<p>test</p>

And that source code produces this output.

<a href=”“>Logout</a>

<a href=”“>Site</a>

<br>
<br>

test

It looks like this is because you’re using the Visual editor. If so, please try in the Text editor.

I tried this code in the text editor and even disabled the visual editor for this page.

begin
[url logout go='home']
test 1
<a href="[url site]">Site</a>
test 2
[url logout]
end

This returns this HTML source code

<div class="entry-content"><p>begin<br />
<a class="d4pbbc-url" target="_blank" href="ogout"></a><br />
test 1<br />
<a href="<a class="d4pbbc-url" target="_blank" href="ite"></a>">Site</a><br />
test 2<br />
<a class="d4pbbc-url" target="_blank" href="ogout"></a><br />
end</p>
</div>

Is there a clue in the fact the href seems to be cutting off the first letter? Is the [url] supposed to return the anchor links or just the url?

That is strange, the shortcode returns only the URL – so something is interpreting it as a link. The text editor should leave it as it is. I wonder if the theme is filtering the content?

The second example there, after “test 1”, produces an interesting result. It’s not running the shortcode at all, and misinterpreting the HTML code. I wonder what happens if you just do this:

<a href="example.com">Site</a>

Does that output correctly?

Or, perhaps the [url] shortcode is being registered by the theme or another plugin. You can check this by going to Dashboard -> Content, at the bottom of the page open Registered Shortcodes: for the [url] shortcode, it should say CCS_URL.

It is a registered shortcode conflict. The [url] shortcode is registered to a plugin I have called “GD bbPress Toolbox”, which essentially is allowing BBcodes in bbPress. And [url] is a bbcode. When I deactivated that plugin, your [url] shortcode worked as expected. ??

I realize this is not an issue for you, but a general WordPress question. Is there a way to get around shortcode conflicts in WP, without deactivating one?

Some Googling reveals that shortcode conflicts are common and there is no “secret” method to use both shortcodes.

For others that may come across this, the [url] shortcode can be deactivated by the GD bbpress toolbox, while still keeping all the other bbcodes. This allows CCS to register the [url] shortcode and all is well again.

Thanks for the responsive support, especially for a problem you could not see on your side.

Great, I’m glad you were able to find a solution. It’s especially nice etiquette on the part of the GD bbPress Toolbox plugin to offer a way to deactivate just one shortcode.

To be honest, the potential for shortcode conflict is something I haven’t solved in Custom Content Shortcode. As far as I know, WordPress doesn’t have a built-in way to avoid/detect shortcode conflicts, and this plugin has numerous shortcodes with generic names like “field”. Often, themes and plugins will prefix their shortcodes to avoid conflict, but I wanted to keep simple names that are easy to remember.

So, I’ll think about how the plugin can better handle a situation like yours. I’m stuck with the shortcode names that already exist, since people depend on them, and it’s not possible for the plugin to detect a conflict – so re-registering the same shortcode by a theme or another plugin is always possible. Perhaps I should allow for renaming the shortcodes, say in the settings page? If you have any suggestions, please let me know.

—

Now that I think about it, there could be a way for the plugin to check if all shortcodes are registered correctly. After all plugins are loaded, it can go through the list of its own shortcodes, and make sure that they’re registered to the expected function inside the plugin. If not, it can display a message and offer a way to change the shortcode name. Well, this might take some time to implement, but it would avoid any similar issue like yours, with unexpected behavior due to a shortcode conflict.