I’m pretty sure my question is very clear. I found a partial answer to my question here: https://www.wpdownloadmanager.com/doc/templates/template-tags/
What I want is to add the
[version]
Returns The Value of Version Field
Usage:
[version]
tag to the title of the package. What I want is for the package page to display the title like this “Chrome 99” (package name+version) instead of just “Chrome”. Not sure which template to edit, especially because the changes I make may be overwritten when updating the theme or the plugin.
Seems to be working now, even though the Gutenberg plugin is…disabled? It seems not to make a difference, like WP loads it anyway? At least my custom taxonomies also work now.
The fact that it is working for you is not helpful. I have once again disabled the plugins that I had running and left only the absolute bare minimum (although the ones I disabled I also need. so that is not a solution). All that is left is your plugins and once again Gutenberg isn’t loading. I have other plugins on other websites running with the latest WP version that use custom post types (just like your plugin) and they work fine with Gutenberg. Your plugin is the only one that has a problem with such a basic functionality. I even managed to get custom post type working with Gutenberg and my programming skills don’t go beyond “echo hello world!”
Like I said, you have my login to the admin, look into what is causing it or reapply the fix you implemented earlier. This whole situation is ridiculous. I really don’t see the point in extending my license once the year expires if this is going to become a recurring “feature”.
Once again Gutenberg no longer works, even though the Gutenberg plugin is installed and active and Gutenberg is enabled in the WPDownload Manager settings. Since you fixed the bug (not that well apparently) Automattic has updated both Gutenberg and WordPress so that may have something to do with why it stopped working again, although, no offense but I don’t understand how something this basic can pose such a problem.
You already have access to the WordPress admin, the login info is the same and mentioned in a private reply above.
Well, I am on the support forum for the Pro version of WP Download Manager so really what could I be having problems with? Oh, I know, the Add New Download page (which is actually called Add New Package https://www.file-portal.net/wordpress/wp-admin/post-new.php?post_type=wpdmpro) of WP Download Manager Pro. Could you please stop asking such pointless questions and look into what is happening instead?
This bug is back, partially. Probably with the new Gutenberg update, Gutenberg now no longer works on packages. “Enable Gutenberg editor for WordPress Download Manager” is on.
LOL, you people really have a lot of nerve to pretend you didn’t know this was there. “I shall check the issue in detail if there exists such issue with this”
I’ve now looked at my site and it appears on my site as well. probably hidden via CSS since it is not visible but it does appear in the source code. And that’s on top of the attire theme placing its own (visible) link. Thanks for the warning OP. I can understand inserting such a link on a free product, but once you’ve been paid for it, doing this is a dick move.
You can also use the WordPress default export-import feature
I know about it, but I don’t see how that is going to help. The WordPress native exporter/importer is for importing content that already exists and was exported from somewhere else, not for bulk content generation.
Yes, it is fixed thank you. Is there any way to use XML for importing/generating new packages as well? CSV files are difficult to edit, because most editors can’t handle commas inside the fields and treat them as separators. Or is there another way to mass create packages with some placeholder content and fill in the details like the download links, file size etc., later? I tried to do that using a WordPress plugin that allows creating mass posts but it seems something doesn’t get added and the packages created like that are broken.
“Access denied” red message where the download button should be?
> Can you please elaborate more on your issue?
Not sure what else to say except what is in that screenshot. Th error happens when I try to export the packages list to XML. The login info is available in this topic: https://www.wpdownloadmanager.com/support/topic/categories-tags-disappear-on-add-new-package-page-when-enabling-gutenberg/#post-165447
So have you fixed this? Surely it can’t be something that requires 7 days…
Sigh, and here I was anticipating it was already fixed…
Go here https://www.file-portal.net/wordpress/wp-admin/post-new.php?post_type=wpdmpro
You will notice that the package default (built-in) categories and tags don’t work (are missing) on the add new package https://www.file-portal.net/wordpress/wp-admin/post-new.php?post_type=wpdmpro
page when Gutenberg is enabled for WPDM packages.
Package categoris and tags seem to be missing when Gutenberg is enabled
When disabling Gutenberg for packages the categories and tags become available and can be set from the add new package page, as can be seen in this screenshot.
package categories and tags accessible when Gutenberg is disabled for packages.
BTW your forum actually strips out links added via the link option when posting a reply.
I literally disabled everything except YOUR plugins and the default categories and tags still don’t show up for WP Download Manager packages with Gutenberg enabled. I mean sure, I could just disable Gutenberg, but it’s not really a solution and I don’t understand how something like this can even happen.
All of the plugins that are active are FROM YOU, except Quform (a form builder), and Updraft, a wordpress DB and site backup solution. Oh, and the actual Gutenberg! In fact I even went ahead and disabled Quform and Updraft on the off chance they might be somehow preventing YOUR download manager and its premium packages from working with Gutenberg, and the problem remains. What plugins do you expect me to disable? Are you serious?
Same problem. As soon as I enable that option and activate Gutenberg, the builtin tags and categories disappear.
I followed the instructions from the screenshot above.
reply #163377
Here is the result.
Add new package with gutenberg off.
https://imgbox.com/KL9GoPUf
Add new package with Gutenberg on
https://imgbox.com/JJBac9dP
List of active plugins (I even disabled everything but the bare minimum plugins to see if it was some incompatibility, but that didn’t solve the problem)
https://imgbox.com/3Few39hL
Since the pictures don’t seem to be loading, I am adding the links to them.
add new package page with gutenberg not enabled, even though Gutenberg works for regular posts
https://imgbox.com/UxZLMuIZ
list of active plugins
https://imgbox.com/a1JHTimt
At this point I am not even sure you are reading my posts.
I told you in the previous post that I already have that plugin installed and active. WPDM Gutenberg blocks, version 2.1.4 installed and active.
Your plugin doesn’t use Gutenberg at all (as if Gutenberg wasn’t even enabled on my WP installation).
See what my “add new package” page looks like, it’s like old school wordpress. Where’s Gutenberg.
See below list of active plugins.
First of all, your last answer is completely unhelpful. I have that plugin installed and active, but Gutenberg is not working in WPDMPro. In fact WPDMPro doesn’t seem to support Gutenberg at all. It only loads tinyMCE by default, because you have not configured the wpdmpro custom post type, or the custom tags and custom taxonomy to work with Gutenberg. I have the latest version of WPDMPro 6.0.6. I would assume it’s the latest, my WP admin is showing no updates in waiting.
https://wordpress.stackexchange.com/questions/324221/enable-gutenberg-on-custom-post-type
Start by registering a Gutenberg WordPress custom type. The process is fairly easy and involves adding the following the code snippet.
add the show_in_rest key and set it to true via your custom post type.
'show_in_rest' ► true,
'supports' ► array('editor')
As you can see, the above code snippet just set the ‘show_in_rest’ parameter to ‘TRUE’. After this step, when you create or edit a custom post type, you will see the Gutenberg editor visible and enabled.
By default, a custom taxonomy panel is not added to the Gutenberg editor. That means authors are not able to select terms in the editor. That’s a problem. In this quick tip, let me show you how to turn on the feature. [It’s pretty easy.]
Does your wpdmpro plugin display the inbuilt taxonomy by default when using gutenberg ?
I think I figured it out. I exported the packages using the wordpress exporters to XML format and compared a post that works with one that doesn’t. The packages that don’t work are the ones that I created using a wordpress plugin for bulk creating posts. Comparing the ones that work and the ones that don’t, it seems that the ones with the access denied errors lack certain custom fields that are hidden (prefixed with _) which are created when using the wpdmpro “new package” comnand, but are missing when posts with the wpdmpro type are created using other methods than WPDM pro.
Now there are two problems:
How do I fix those entries that are broken? (how do I add those missing fields to them so I can fix them)?
Won’t this create problems with form builders that allow us to create custom post types since only posts created with the WPDM Pro menu work? I am using a form builder called quform (https://www.quform.com/)?
Your forum software replaces = > (without the space) with a right pointing triangle so your code isn’t going to work unless someone knows the syntax for PHP. At any rate, I figured out what was wrong with my code and now my custom taxonomies display in the post list and in the individual post editing interface. But… the native taxonomy (categories) your plugin defines for the wpdmpro custom post type still doesn’t load when creating/ editing a single post individual post (I can only set it via the quick edit option in the package list).
No answer?
1. Well, that’s an embarrassing case of temporary blindness.
2. Not sure if I did something wrong but the login page I created following your instructions replaces the URL for the admin login page. This also creates problems with a plugin I was using, called “Restricted site access”, which expects the admin login URL to be standard and can’t handle the redirection made by your login page.
Instead of /wp-admin/, your page does a redirect wpdm-login/?redirect_to=https://www.mysite/wp-admin/
3 and 4. I found them. I solved the issue at point 4. I will have to read those sections of the documentation to get more familiar with the options and what they do.
Thank you.