Jason Emanuelson

Nevermind.

Could WPDM use AI to updated the changelog on the WP repository like nearly every single other plugin on the WP repository does?

Guessing you did not read the rest of my post. It is not about today. It about thinking about the bigger picture. You put AI in the main settings, which means you most likely plan to implement it elsewhere. But, because there is no guidance on your direction, people are left to wonder. The AI Settings assume you will pick one or another AI vendor, but fail to consider that maybe people don’t want it at all. Why must developers assume we want AI in everything?

As far as making templates, your template builder is actually very easy to use. There are a few features we wish it had, but otherwise, it is very capable and very easy.

On a related note, what would you say if I just told people to have Claude write their own version of WPDM? Would Claude understand all of the nuances that your developers have put into WPDM? No. It may have the basic knowledge, but not the experience. Would it be able to keep it updated for the evolving web and threat vectors? No. Would it factor in the need for developers and support personnel’s jobs? Again, no. It might be the shiny squirrel, but there are so many reasons to take a measured approach to AI, but instead, throw caution to the wind and march to putting it into everything before really thinking about what is the end game?

As much as you and I disagree on things, I still would rather interact with you than a datacenter. I would still rather pay for a license to have a person help me than a machine that took those people’s jobs.

ALL OF THEM. AI should be opt-in, period. Some of us have to deal with compliances and regulations, and until developers (not just WPDM) start factoring that in, it should be a feature that can be turned of in entirety.

Want to win our trust for AI? Set a clear AI policy: what you will do with it, what you will not do with it. Where the sources of information are, and what gets transmitted where. Is it being used to build any foundations (internal and.or external) models. AI should be treated as reverently as privacy and security policies, but because everyone wants the wet dreams of AI sprayed everywhere, no one thinks about the clean up afterwards.

AI is very similar to letting a robot loose in your home. Right now, it can just say a few things and walk around. But, the brain is building, and with that, the functionality will follow. Someone has to think about what happens as those features and capabilities grow, and what happens if somehow that functionality can be taken over. Whether it be a city, a non-profit organization, a school district, or a mom-and-pop small business, websites are like homes, and they need to have someone that thinks before just bringing home the newest shiny squirrels (or whatever tech) and just letting it loose within the home (or site).

In our case, we have to deal with municipalities, county governments and state governments. When AI is just thrown in, because you can, rather than asking what the ramifications for it are, you make tools like WPDM hard to consider and candidates for finding alternative solutions. This race to AI everything will catch up to those that only looked at it as a race, rather than as something that needs time to mature and be tested.

So little concern is given to any of this, especially in communicating to the public what is going on with a brand new technology that has exponentially growing capabilities, yet people like us are just trying to be responsible and ask companies and developers to think about these things.

Please start publishing the change log to the WP Repository and not just to your own change log page. Having to go look at your page every single time there is an update, when nearly every other plugin puts a changelog with updates on the repository should be a minimum.

I understand.

I was not necessarily asking for free. I just wanted a solution that was not $500 or $50/yr for something that would never change again.

I said at the top of this that I need ONE (1) single field. I don’t need any of those other features. I just needed a separate date field. You’re trying to sell me a mansion or a renovation, when I just needed a way to hang a calendar on a wall. This is how and why people start rolling their own solutions. Will they do everything yours will do, no, but they do what the once-paying client needed/wanted.

So, $50/year or $99/hr? Last time I checked, you had something like a $500 or so minimum on any customization. For a plugin we only use the most basic of features, but license pro to support the devs, adding a second plugin that only is used for a single date field is a tough one to even consider.

Not sure why it lost connection, but got it back. Thank you for the help.

Nevermind. Why does WPDM Pro need 128MB of additional memory? The idea that a lesser used plugin on this site requires 128MB of memory seems a bit excessive.

Thank you.

I also asked about how to get this added to the feature needs list?

I suppose I should have asked it in another way, with a use case.

Is it possible to use a download page template to auto-download the file? This is a common use case and delivery mechanism for software titles. Click on the download, a page opens, and a few seconds later, the software begins to download, but if it does not, there is a direct download link as a fallback.

If none of this is possible, how do I get it on the feature needs list?

Wait, I have an idea.

Is it possible to set the default action of the download package page to redirect to it’s download link directly?

What email address can I associate it to?

I will get you admin access. I am just waiting for an approval response from the client.

Feature requests are well and good, but way out of the scope of time. Is there any workaround or easier way than hundreds of manual copy and paste, then labelling actions?

I might as well just put in posts with format set to link and pull them all as categorized posts, but again, was trying to utilize DMPro.

I guess the frustration is that I will eventually have dozens, if not hundreds of links that will need similar treatment, as the city wants to have all of its documents available via menu, rather than on a page. While it would not be our suggestion to do it that way, those are the requirements that we have to follow.

If I have to go back and forth between screens for dozens or hundreds of links, I might as well just use direct file links in the menu, rather than download manager pro to accomplish this.

While that may work, it means it has to be updated every single time any changes are made, rather than being like the selection option that already exists in the menu builder? It also adds a layer of complexity that is not the case when using the existing menu builder option.

It would be nice if we could simply select in the menu builder whether we want download page or direct download link.