Hello,

I just installed the plugin on an October 2.0 instance and unfortunately encountered some problems.
When I try to access the settings I get the following error:

Undefined variable: prompt
~/plugins/linkonoid/mrevisions/formwidgets/fileimportexport/partials/_file_single.htm line 43

I was able to fix this in a hurry. However, calling the details of an old revision does not seem to work either.
Are there any plans to make the plugin compatible with October 2.0?

Thanks & greetings
Martin

Hello,

Unfortunately, I stopped developing for OctoberCMS due to recent events and completely switched to the Golang stack during development (the last thing that kept me in the PHP world was OctoberCMS, but recently the project "died a little" for me, and before that there were a lot of questions to this project in terms of performance and Laravel versions support).

I don't think that support for v2 will appear someday (I haven't decided yet, it depends on the number of requests and further "exhaust" from the marketplace). In addition, according to the new rules, this requires financial investments (by the way, the profit from the marketplace is so small that it is economically impractical, besides, I am afraid, it will be even worse in the future ...).

What to do? As soon as the WinterCMS marketplace appears, all plugins will be transferred there and I guarantee their support for this CMS. A number of unical plugins will also be placed there, about 9 pieces that are not currently on the marketplace (which were in development, or have a prototype, but have not been brought to production).

In any case, ask questions (better directly on email), maybe I can help you with something or suggest a way to solv.

I hope for your understanding (like many other developers of solutions for OctoberCMS, I "hostage" to the "strange decisions" of the founders of this CMS).

Last updated 3 years ago

In addition, according to the new rules, this requires financial investments

This is not accurate. We provide developer licenses for developers on the marketplace, you simply need to contact us via email.

Sadly, there is a lot of misinformation being spread around about the project at the moment.

Thanks to Sam for the information (including in a personal email). I don't really follow the OctoberCMS news. The latest information on this was that developers need to purchase a license for the project (sorry if I was wrong). The price of the issue is low, the essence is somewhat different, the explanations are below.

I perfectly understand the reasons for this decision from an economic point of view (we are talking about the commercialization of the project). Perhaps the money from the site is very small and does not justify the financial investment in the project (I am not in the know, so I can judge indirectly by myself). I'll make a reservation right away - I never create plugins on purpose (this is economically impractical, since I specialize in the Go-stack), plugins are a by-product of projects (there are exceptions - plugin development on demand, via funding by the customer and the right to place the plugin on the marketplace), where I involved in role consultant-developer, and clients asked me "To do something to make it faster and more convenient", as a result we get a kind of plugin prototype that needs to be finalized before public placement (sometimes it takes longer than finalizing the project itself, since you have to make a "general decision" from some "private solution" suitable for use on the Marketplace).

Now about the problem itself. In fact, there was a division of a small group of OctoberCMS supporters into 2 camps. Obviously, this is a big problem for the developer. Now the question arises before me "where to go", since it is physically problematic to support several plugins at the same time, and in several versions (branches). And given that OctoberCMS has become paid, the trading platform immediately narrowed and it is obvious that the return on it will also decrease.

On the other hand (this is a positive moment) OctoberCMS has left a "paid audience" who knows what they want and is ready to pay for some more or less unique solution that saves time for project development (it is obvious that new plugins like "new super-Twig -filter" will be much smaller on the marketplace, since studios don't need them).

Last updated 3 years ago

It's understandable that the change is a shock for many. However, we feel it is the best thing for the sustainability of the project in the long term.

To the original point. We can arrange a developer license any time by sending us an email.

Last updated 3 years ago