Can web user create a resource?

fabryshock

hi all, Is there a way to make a web user create a resource via a plugin? in modx evolution there was ResourceEditor which worked fine, but now it doesn't work anymore.... :-(

many thx

fourroses666

I don't have the answer but what version of EVO do you use? Doesn't work because of PHP?

fabryshock

i use the version Evolution 1.4.15 and PHP 7.1.33 but the snippet ResourceEditor is very old...

Pathologic

FormLister

mamta25

The old ResourceEditor plugin doesn’t work in the new MODX anymore. But you can still let users create pages by adding a simple form on your site and using a small piece of code that turns the form input into a new page. It’s best to let only logged-in users do this and make sure to check the data to keep things safe and avoid spam.

Dmi3yy

We have in core this class
https://docs.evo.im/03_develop/06_di_v_evolution_cms/06_documentmanager.html

it done special for case when need create Documents (need translate into English but I think it not a problem you can use AI or translator)

Dmi3yy

We in progress with task what we have in EVO and how work with new Laravel components

there a lot of info what need translate and public on site

https://modx.evo.im

but now one want help with docs so then need wait when we will have time for that.

Animatorali6

That’s a good question, letting web users create or manage resources can be really powerful when done right. Since ResourceEditor is no longer supported, you may want to look into custom plugins or lightweight frontend forms that handle permissions securely.

For streaming-focused platforms like rbtv live (sports streaming apps), a clean and controlled way for users or admins to manage content is key to keeping everything fast and organized without breaking the core system.

Dmi3yy

I think this is actually a great moment to talk about community involvement.

Right now, the core team is actively working on and investing time into the further development of Evolution CMS. But at the same time, the community itself is very quiet and passive — and that makes it hard to move in the right direction.

It’s important to understand one key thing:
the first step is not implementation — it’s the request.

Not everyone needs to know how to build a solution. That’s totally fine.
What really matters is clearly describing:
• what problem you’re facing,
• what hurts or blocks you right now,
• what you wish Evolution could help you with.

If users don’t understand how something should be done — that’s actually the best reason to create a topic on the forum and explain the pain. From there, we (as a core team) can show possible approaches, patterns, or even implement missing features.

If you have ideas, problems, or feature requests, please:
• start a discussion on the forum or
• even better, create an issue here:
👉 https://github.com/evolution-cms/evolution/issues

We actively read and work with those requests. In fact, almost everything that was reported there has already been addressed.
At the moment, there are only about 5 active community requests — which clearly doesn’t reflect real-world usage.

If the community doesn’t say what it needs, how can it expect those things to ever appear?

Now that Evolution CMS development is active again, this is the perfect time for the community to also step up, share feedback, and help shape the future of the product.

cimt67

Hello Dmi3yy Dmi3yy ,
I’ll try to explain what I think as “Webdesigner”.

In my opinion, everything should be easy to install and easy to upgrade. Also, everything should be consistently in English — including code comments and descriptions — like WordPress and similar systems (just for clarification: I don’t like WordPress). But I think this is the only way to attract new users worldwide and to build a strong foundation and long-term stability.

In the last years everything felt uncertain and without a clear plan, and most users don’t like that. I hope you see it the same way.

Here is my list of questions:

Where do we belong now? Evo-Community? Or simply Evo?
I’m sure many people are asking this. Which Fork has a future?

What most “Webdesigners” want — also in the future — is the classic installation process with install.php, without requiring console tools or Laravel.
Most of us are not developers!!! And many users have small shared hosting packages that do not support this!

Updates directly from the manager/backend.

The forum and the Evo source code / descriptions should be only in English. This gives most new users a better feeling — we need to think globally.

English is not my native language and I don’t speak it perfectly, but it’s still better to use only English instead of mixing English and Russian.

Evo users love building their websites individually using chunks, snippets, TVs, etc. For most of us, that’s all we really need.

Standard components like:

DocLister
FormLister
PhpThumb
if-snippet
SimpleGallery
TinyMCE4
Pagebuilder
… are very important (for me)!

fourroses666

We need to keep the simplicity of building sites. (and for our users which use the manager)

Some things I wish that would be improved which come in my mind:

I think the manager needs a framework. But I can understand that will break allot of existing modules/plugins and the tree. That task is uge. Developer uses their "own" styling.
Installing plugins/modules on add-ons (extras) with one click. Like we have but that doesn't look very good and have so many old packages. Needs to be sorted.
A decent image/file/media manager. The current one MCPUK works but if there are more modern options I prefer that.

I still use TinyMCE 4 because it has the internal linking (search in evo [_id])

Dmi3yy

Graffx Design About Search in EVO

Spending years sticking to an outdated solution instead of spending five minutes to write a message like “hey, we’re missing this feature” feels… inefficient. Especially in an open-source ecosystem, where no one can magically guess what you need unless you ask 🙂

Open source doesn’t really work on the principle of “someone will surely do it for us one day”. It works when users communicate their needs — even just by asking.

For the record: Search in EVO works perfectly fine in eTinyMCE 8.3.2, so this isn’t a limitation of newer TinyMCE versions at all.

You’ve been using EVO for years — asking for the features you need is probably the easiest part of that journey 😉

Dmi3yy

One more important clarification about our strategy.

We do not break or rewrite legacy functionality. This is a deliberate choice.

Evolution CMS is used in live, production projects that cannot be stopped or rewritten. Because of that, our approach is to keep legacy stable and add new functionality in parallel, so projects can upgrade gradually, step by step, without downtime.
This is exactly how we work with our own client projects.

At the same time, Evolution CMS is actively evolving, and here are some concrete examples of what is already done:

🧩 New Installer

We have built a completely new Installer, which is currently being actively tested and finalized:
👉 https://github.com/evolution-cms/installer

This will significantly simplify installation and future upgrades.

🖼 New File / Media Manager

There is now a modern file manager available, designed to replace older solutions over time:
👉 https://github.com/evolution-cms/eFilemanager

It’s actively developed and ready for real use.

✍️ TinyMCE 8 for Evolution

We’ve assembled and integrated TinyMCE 8 specifically for Evolution CMS:
👉 https://github.com/evolution-cms/eTinyMCE

Internal linking and Evo-specific integrations are supported and can be extended further without touching legacy editor setups.

🔐 Modern Authentication (Passkeys)

We also introduced a component that improves authentication logic using passkeys:
👉 https://github.com/evolution-cms/ePasskeys

This is an optional, modern addition that works alongside existing authentication mechanisms.

⸻

All of these improvements are delivered as optional components, not breaking changes.
You can adopt them when you’re ready, without stopping your project.

If the community needs additional functionality or improvements, please open an issue and describe it clearly:
👉 https://github.com/evolution-cms/evolution/issues

We’ve already closed many old issues and are ready to work on new ones.
Evolution CMS is being actively developed — now we just need the community to actively participate.

Dmi3yy

I’ve spent the last 3 years building an enterprise product, and only recently shifted my focus back to EVO.

I know how to build things. What is critical for me now is understanding what the community actually needs and how it uses the product. And that’s the problem — the community is practically silent.
This is an open-source project, after all.

For me, EVO is not something new or experimental. I’ve been using it for almost half of my life. Now I’m packaging that experience into a real product.
Development never stopped — all new features are documented and published on GitHub.

What I genuinely don’t understand is why a developer is expected to chew everything up and put it straight into someone’s mouth.
If users can’t articulate how they use the system, what problems they face, or what they actually need — then what’s the point of “doing something for the community”?

We’ve been developing this project continuously since 2017.
And while users correctly point out issues like language or communication, that’s exactly why this forum exists — it’s the official English-speaking platform. Yet it’s silent.

I’m sorry, but I’m not going to do marketing for an open-source project.
The moment real resources are required, that becomes paid work.

The core target audience is webmasters who understand content and layout.
There’s no reason for me to focus on users who will never pay anything.

So yes — the result is simple: if you don’t need it, that’s fine.
I’m building it the way I need it.

Now Sergey has joined and is doing the same — building it for his own needs.
So today, we’re building this primarily for ourselves.

And that’s honest.

cimt67

Hi Dmi3yy,
now I understand!

@So today, we’re building this primarily for ourselves.
Thanks for the clarification!

Dmi3yy

Yes, at this stage we are indeed building this primarily for ourselves — and it’s important to clarify what that actually means.

It means that we are doing the real work:
– researching what the system truly needs;
– identifying and designing the required modules;
– implementing and thoroughly testing them;
– proactively proposing and validating new features.

At the same time, the “community” mostly limits itself to general comments like “everything is clear” or repeated complaints — without concrete proposals, designs, code, or actionable input.

In this context, it feels rather strange to see complaints coming from people who are not contributing, directed at the team that has been maintaining and evolving this system for over 10 years, investing time, expertise, and responsibility into it.

We are always open to constructive ideas and real contributions. But until those appear, we will continue doing what we do best: actively developing the product and moving it forward, rather than waiting for abstract feedback.

Leah_Casper

I’ve been trying to figure out a clean way to let users submit content from the front-end without giving them manager access. This approach seems much more straightforward than the workarounds I was looking at.

Dmi3yy

Leah_Casper working on this soon will be demo