Matthias Pabst

@raldea89 We can continue the discussion here. The problem also exists without using the addon. I just checked this with a another website where I use the free Download Monitor plugin only. The result:
– default templates: frontend.css is loaded
– custom template: frontend.css is not loaded

The shortcode I use on this site is very simple:

[download id="160"]

@raldea89 Hi! I’m using Download Monitor 4.5, the Page Addon 4.1.4 and the Classic Editor plugin. The shortcode is:
[download_page posts_per_page=100 show_search=false category_limit=10 include_categories="26,27" front_orderby=date]

Hi John,

I found it. The plugin FV Flowplayer Video Player breaks the Breadcrumb NavXT settings page. You only need to activate the video plugin – then visit the settings page “/wp-admin/options-general.php?page=breadcrumb-navxt”. You should see a fatal error in the categories area.

Is this a problem with your plugin or with the Flowplayer plugin?

Best regards
Matthias

Hi @codepeople

Thank you for the very fast fix! Now all files are loading from the webserver.

Best regards
Matthias

4.4.6 fixes the problem for me. Thanks!

Same problem here: error 403 for all download links after updating from version 4.4.4 to 4.4.5. All download links redirect to the files, which are blocked by the .htaccess in the dlm_uploads folder.

And also the same: the redirect to file option is and was not checked.

@arisoft Thank you! This helps.

Would be great, if this would work by default without a custom selector.

Thank you @zgrossbart. I will hide the menu items via admin-styles.

Hi @wpmudev-support1,

thank you for your reply.

Cheers,
Matthias

I was a big fan of the plugin auto-updates and used it for about 75% of all plugins on over 40 websites. Now I deactivated auto-updates for all plugins because I don’t want such a bad surprise again. I think a lot of people will lose trust in auto-updates and this is very sad because its a great feature to make websites more secure.

I asked the plugin review team about their opinion about this rebranding. This is what they answered:

`What plugin authors decide to do with their plugins is not really our concern. It may be unpopular, but unless it’s doing something actively malicious, it’s allowed.

The plugin changes may be unpopular, but that’s how things work. People can stop using the plugin or switch to another plugin. All these plugins are free, after all. We’re not paid for them. Nobody pays anybody anything, we only host a free repository here.

Also, remember that these plugins are all open source. The code is entirely free. If somebody wants to take the older version of the code and submit it as a fork for users to switch to, then that’s entirely plausible too…

Sometimes, you have to let people figure things out on their own. Simply telling a plugin author that a full overhaul with a bunch of new stuff is a bad idea isn’t really going to get you anywhere. They have to screw it up themselves and have the people tell them so, in order for them to figure out where they went wrong.`

This is a complete new plugin with tons of features I’ll never need! Why did you do this?? I will have to delete it from many sites. ??

@logologics To develope the add-on you need the code of the parent plugin (Gravity Forms). Its not enough to use the demo site. ??

@abdultikweb I hope everything went well with your dev license. Can you give us a hint when you will fix the bug? Thank you!

I received the same reply.

Chris replied
Feb 4, 10:35am
Hi Matthias. We have a contact from Kasper today and that has been assigned to our community lead. When I hear something back about the status, I will let you know. Thank you.

@abdultikweb Thanks for the email. I’m in contact with GF support.