Lana Codes

I have not experienced such a compatibility problem.

Please try to update the permalinks, in the WordPress admin on the Settings > Permalink page, click Save Changes, this will update everything and try again.

Please also check the download permalink in the Lana Download settings.

You can use it with jpg and png, but for security reasons specifying the absolute path is only possible with an addon plugin, which you can download from here: https://lana.solutions/plugins/lana-downloads-manager-abspath-local-file-addon/lana-downloads-manager-abspath-local-file-addon.zip

But the best solution is to upload the images via Lana Download in the WordPress Media Library.

In the case of images, you can also specify a URL instead of a path, if it is also available to you.

The plugin works, but the files will also be directly accessible from the lana-downloads folder, which means that if someone downloads it via direct download, the counter in the plugin will not increase, and the download will not be logged.

I think it can be solved with the following Nginx configuration:

location /wp-content/uploads/lana-downloads {
deny all;
}

You may need to specify an absolute path for the folder.

The category widget addon plugin does not contain a shortcode, only a widget.

At Elementor, when adding a widget, you will find the “Lana – Download Category” widget in the “WordPress” category.

Please note that as far as I know, the Elementor widget search field does not search in the “WordPress” category. So you have to find it manually.

It is possible, for this you need to list the downloads, which is a custom post type.

There is no such built-in list in the plugin. However, it can be solved relatively easily with custom development.

If you want a unique solution, like listing the categories with a widget, even adapted to the design of the WordPress theme, you need a unique solution, which we can do as a freelancer assignment.

We are planning to create a category list widget in the addon plugin, this would be useful, but unfortunately I cannot give you an estimated time to create it.

Currently, the addon plugin only has a download by selected category widget.

Post type and taxonomy archives are supported by WordPress by default at these URLs:

Category archive:

http://localhost/download-category/online-docs/

You can see the category endpoint in the settings. It only works if public is enabled.

But it only lists downloads within the category.

There is no WordPress core solution for listing all categories.

The Lana Download Category Widget is primarily designed for page builders.

Compatible page builders include WPBakery Page Builder and Elementor.

If you use something else, please write to us and we will try to help.

@ipstenu You’re right, I should have written “the WordPress block development team” instead of “you”. But you are currently the only one representing the WordPress team because no one else has commented here… And I don’t think I wrote anything mean or hurtful, I just expressed my opinion.

You also wrote:

I personally have only a theoretical knowledge of the issue, so I can’t help out there.

Well, I also have practical experience and knowledge of what this vulnerability can cause.

Any shortcode vulnerability like contributor+ shortcode XSS, LFI or SQLi will potentially become an unauth vulnerability.
If you’re wondering how much of a problem this can cause, I alone have reported more than 400 shortcode XSS vulnerabilities in plugins. Among them in plugins with 100k+ and 1M+ and 3M+ active installs.
I think you also noticed this, considering that as far as I know you manage these reports at www.ads-software.com.

Note that now everyone is sharing codes on how to enable shortcodes in block templates.

So it should be written everywhere in very large and highlighted letters that the vulnerability in block templates makes other shortcode vulnerabilities unauth vulnerabilities, which can be very serious.

@ipstenu Yep, I don’t think you’re developing Gutenberg, or specifically Blocks in Core (since I’m a plugin developer, I know what you do at WordPress because you’ve checked my plugins). But when you say “they”, it may mean another department at WordPess team, but to me “you” means like the WordPress development team, all departments.
And you’re almost the only one from the WordPress team who answers the questions now.

I thought that “since Full Site Editing is the way to go” was your personal opinion. But I think the WordPress core team thinks the same. That’s why I answered like this.

So obviously I meant that the WordPress core team, project leaders or Automattic or anyone in a decision-making position at WordPress should have decided to write a separate block CMS.

I could also have said that you should not have enabled the beta Gutenberg during the plugin review (maybe it would have even been a little funny). Or it should have just remained a plugin. Think how easy it would be now, just disable Gutenberg and switch to another theme, and everything is solved.

But now it will be the same, only in a different way. Block templates will be disabled. The users will decide.

And, in their defence, it’s 2023, and using shortcodes in the modern block-templates maybe should have been disallowed from the start, since Full Site Editing is the way to go.

@ipstenu

Yes, you could have done this by creating a new project called BlockPress and leaving PHP based WordPress alone with the JavaScript block nonsense.

You can easily check the user feedback for the Gutenberg plugin and the active install number of the Classic Editor plugin.

You’d be amazed to see the amazingly complex things that average users use shortcodes and plugins for. You are taking it away from the users and saying “here you go, but you can edit blocks within the limits we want”. But everyone used shortcodes, everyone knew how to do it, even if it was more complicated and “not so user-friendly”.

So yep, you really shouldn’t have mixed the classic editor with shortcodes with the block editor. Moreover, you should have done this by creating a separate CMS for the blocks, but no one would use that, just as no one used Gutenberg as a plugin.

Well, you’ve removed the shortcodes from the block templates, now we’ll see again how many people choose blocks instead of shortcodes.
Then I hope you will realize that it would be more worthwhile to develop Core based on user feedback.

lana-downloads-manager-pdf-viewer-addon.zip

The best way in this case is to create a child theme and override the post template file. If you write me an email at [email protected], I can send you a child theme.

If you send the link of your website, even privately via email to [email protected], I can prepare the appropriate CSS for the Lana Download button for the theme you are using.

If you want a button, you can use the [lana_download] shortcode.

The button has a style for Bootstrap-based themes, for other themes you may need to add custom CSS, which you can do in the Customizer.