Seeing extra symbols on the download button

Hi ecn I just tested the new version and created a download button, and I tested using fancy 0 and fancy 1. I don’t see the greater than symbol in my download page.

Try to test a different theme like Twenty Fourteen or Fifteen. See if that helps you.

Kind regards

The site is not visible yet, unfortunately, so I can’t direct you to it.

I just reinstalled a fresh install of the plugin and no luck. In fact, that was after today’s pushed update of the plugin. Still the same.

I have tested this on various themes.

Where would I begin to look for this code? It renders in the download link itself without short codes so is that Fancy 1?

I attached a screen shot of what I get when I float over it. I cannot tell if the extra characters are rendering appended to the title, prior to the word “download” or other.

View screen shot in Dropbox here

That is very strange, can you share your shortcode?

As such, it’s not a short code. I suppose it is whatever the default renders. It’s just the link to the download itself, so whatever template is applied out of the box. The URL is below. It happens on all my downloads. Basically, if I click on the download link, I get the extra characters in the result.

https://manzanillosol.com/sdm_downloads/manzanillo-sun-january-2016/

Are you adding any text in the shortcode?

I am not able to reproduce this error in my testing platform.

If you are not adding any text in the shortcode and the text you add when creating the download does not have any spaces or fancy characters then you can try the following. Disable all your other plugins except this one and carry out a test.

There is no short code. It is just the download link itself. It renders without a short code. What I mean is, I create a download item and give it a category, tags, a thumbnail image, etc. and save. It creates a URL with the structure of the one I sent. I can give you access to the site to look if you send me an email address. In any case, it is independent of a short code structure.

Additionally, if I use Fancy 0 or 1 in a short code, it does the same thing. Fancy 2 doesn’t.

Here are screenshots of my process

Here is the version of the plugin (downloaded today though the same thing happened before the update)

Okay try the following change the title to something very simple, like PDF Download.

See what happens.

Just tried that and no luck. It truly looks like there’s some incomplete code in the plugin package but I cannot find it and, strangely, seemingly nobody else is having the problem.

Try deactivating all your other plugins except this one see if that helps you.

So, the good news is that that fixed it. The bad news is, I have no idea what was causing the conflict. Also, I now have this error on the front page and errors on the back end.

Notice: Constant WP_DEBUG already defined in /homepages/23/d187487723/htdocs/manzanillosol/wp-config.php on line 87

Whenever I activate a plugin (starting with SDM only), I get this as a result. I can go back and work in the dashboard but it’s like it punted me over to front end on activate plugin. Right now it’s on Twenty-Thirteen for testing.

Notice: Constant WP_DEBUG already defined in /homepages/23/d187487723/htdocs/manzanillosol/wp-config.php on line 87

Warning: Cannot modify header information – headers already sent by (output started at /homepages/23/d187487723/htdocs/manzanillosol/wp-config.php:87) in /homepages/23/d187487723/htdocs/manzanillosol/wp-includes/pluggable.php on line 1228

Warning: Cannot modify header information – headers already sent by (output started at /homepages/23/d187487723/htdocs/manzanillosol/wp-config.php:87) in /homepages/23/d187487723/htdocs/manzanillosol/wp-includes/pluggable.php on line 1228

Warning: Cannot modify header information – headers already sent by (output started at /homepages/23/d187487723/htdocs/manzanillosol/wp-config.php:87) in /homepages/23/d187487723/htdocs/manzanillosol/wp-includes/pluggable.php on line 1228
1

This new notice that you shared has nothing to do with this plugin. It looks like your wp-config.php file has multiple definition of the same PHP constant. Edit your wp-config.php file and make sure you only have one instance of the WP_DEBUG constant definition.

Hi those issues are not related to the plugin. You will have to research them further from your Host. There is definitely some issue on the back end. You could try and reinstall WordPress 4.4.1.

Do you know if you have enabled debug mode in wp-config.php file?

Notice: Constant WP_DEBUG already defined in /homepages/23/d187487723/htdocs/manzanillosol/wp-config.php on line 87

If you have you can turn debug mode off and that will remove all your warnings listed above. But at the same time I would also investigate those warnings and why they are showing up.

Thank you for the help and to pointing me to the config file. I redid it from scratch and updated WP again (though it was the latest). Solved the header calls and debugging. The real culprit was a conflict with Mark New Posts. Sorry to have you chasing your tails. Really appreciate the help.

Glad to hear you solved your issue ??

Enjoy the plugin