dotnetic

Use Adrian's solution

@louisstephens I had this discussion in the inital topic "Revamped module install interface" and @kongondo replied but I am still not convinced and think active and inactive would be better labels. What do you other guys think?

Did you fix it? I am getting a success message: First you should install TracyDebugger. If you are logged in as a superuser, it will provide a nice debug bar, which catches and reports errors. Secondly you can look at Setup > Logs. There you have an error and an exceptions log.

@Peter Knight The filters for installed uninstalled could be also seen as a category and I think I will integrate them into the category select. "Show only uninstalled" are modules that are already downloaded but not yet installed. I am not even sure if this option makes any sense. Picked, is not an option. It was just a demo, which of the filter I selected.

Possible concern about including the module in the core: The module depends on vue.js which adds a new library to the ProcessWire ecosystem. I am biased about using vue.js as it allows two-way-data-binding. So when something changes in the module JSON file, changes can be reflected instantly without reloading or rerendering the whole view. It also allows to quickly filter modules, much quicker than it was possible with HTML which is in the DOM.

Hey Peter, feedback can be provided here, so everyone is on the same page and can discuss together. I am sure you guys will find some more things to talk about, as soon as I publish the module. There is a thing that I am not really happy with, but have to find a better solution: The vue template is embedded right in the module's php, and I would like to change that, so an external automatically genererated (vue-cli) HTML file will be included. Maybe some of you are experienced with this and can help me out. I hope to find time at the weekend to publish the current state of the module.

Because Soma's module is called ModulesManager. This module is meant as a successor to ModulesManager. Regarding question two: Yes this is possible. The option to download a module from a URL will be added also.

Modules Manager 2 provides an easy to use interface to download, update, install, uninstall and configure modules. It is meant to provide an optimized alternative to the core ProcessModule dashboard. Maybe @ryan agrees to merge it to the core at some point when it is finished and polished. Features: Seamlessly download, update, install, uninstall or delete modules Live-Search (aka find as you type) for module names Live-Search (aka find as you type) for categories Browse new and unkown modules from the modules directory on modules.processwire.com Choose your favorite layout (cards, reduced cards, table) Modern UIKit design (therefore only works with AdminThemeUikit) Caches the module list from modules.processwire.com directory locally. What is Modules Manager 2? Why a new module manager? Some people including myself think that the actual module installation in ProcessWire could be improved in some places. Make it easy for ProcessWire beginners and power users Offer better discoverbility to find the right module Make it easier and faster for powerusers to manage modules A manager that list all official modules is a feature, that many other frameworks/CMS's like ModX, WordPress or PrestaShop have by default. What are the disadvantages of the actual core module interface? Installation of a module is not very user-friendly: You have to be aware where to get new modules, search for a module, copy or remember the module name or URL, go back to your ProcessWire installation, paste the module name(URL, click on "get module info" and finally install the module It only displays installed modules, not the ones that are available in the modules directory Uninstalling a module requires you to go to the module detail page, click a checkbox and then submit the change. After that you have to go back to the module overview page. It only displays installed modules, not the ones that are available in the modules directory, so it makes discovering modules hard BETA software Use this module at your own risk. I am not responsible for any damage or unexpected behaviour. Some things might not work fully, please see the TODO list for details. I need your feedback and help This module is still in development and I am happy to discuss with you and get some feedback. What do you like? What is missing? What could make the process even easier? Ask, suggest or provide pull requests. You can download the module at https://modules.processwire.com/modules/modules-manager2/ or from Github: https://github.com/jmartsch/processwire-modules-manager2

10.5 and 10.50 in terms of calculation is exactly the same. If you need this for output on the frontend side, then you could do a simple PHP number_format.

You're doing a needless check, because your query already returned only pages with `in_evidenza=1` $in_evidenza = $page->in_evidenza; if($in_evidenza == 1) { Your code could be simplified (untested): wire()->addHookAfter('Pages::saveReady(template=articolo)', function($event) { $pages = $event->object; // this should also be not needed foreach($pages->findMany("in_evidenza=1") as $new) { $new->setAndSave('in_evidenza',0); } });

Ok, I found one solution but I don't know if it is the smartest way: $('#pw-panel-shade', window.parent.document).click();

Actually you can do this with a simple native JavaScript command inside the panel: window.parent.document.activeElement This returns the element that triggered the opening of the panel.

@ryanI have an open pw-panel, and now I want to close itself via JavaScript from inside the panel. How would I do that?

@Gabriel Uribe Take a look at the configuration of the typeahead script. There you find a setting "maxItem" where 8 seems to be default (not checked). Set it to 0 or false to display all results, or to the number you would like to display.

You see that there is an error in strings.php: The view variable is not set, and you try to modify a property of an object that isn't there. The view variable is available after the TemplateEngineFactory module is loaded. And make sure that in the settings of TemplateEngineFactory "API variable to interact with the view" is set to "view". So maybe you have to change the load order when strings.php is included.

@bernhard You still rock ? Thanks for this tip, this is also possible for PHPStorm, snippets are called Live Templates there. This is a great timesaver.

@ryanIf you try to log in, if you want to change some information, then the form submit redirects to a wrong URL and you are not logged in.

Hey @bernhard If you like, I would to share my experiences with Tabulator inside of PW (without using your module). I implemented working PW panel links inside the Tabulator, that update the table after changing a page (but the solution is not yet optimal) and virtual rendering and also grouping. I think these things would be great for RockTabulator. If you like to get some information, you can contact me on Skype. I do not have enough time to write a tutorial right now.

Hi @bernhard. Maybe you'd like to update your code to the new syntax which awaits a ok and cancel function. See https://github.com/processwire/processwire/commit/63cba339e4cb942885d9702e9d9003539f1b8230 for the syntax.

Yes, I thought about an addition. Right now it's a general purpose module, and a calculation result field would be an enhancement. Besides of that, I really like RockMarkup

@dragan Sure, this is possible with a hook and thats how I do it now (without using RockMarkup). @bernhard It would be ideal, if RockMarkup could create an additional field on demand for saving the value (but then we should be able to select the options, like an integer with max 10 digits, for this hidden field), or if you could connect/link RockMarkup to an existing field, which has it's type and validation defined, because it is a regular ProcessWire field. So the result of a calculation would be saved in this field. Right now I just experimented with RockMarkup and it worked as expected, but saving the value is stopping me from using it right now for this purpose. But I think I will have other uses for it in the future.

Can I save a value for the custom markup field and output it's value on the edit page? Right now I have a calculation field whose value is calculated via JavaScript (depending on other fields). But now on page save, I want to save the calculated value to the field, so I can possibly output it in a Lister Pro column. Is this possible or can you make it possible? I think this would be a cool addition, because you can use the value on pages/listers, where the other dependend fields are not available.

This is so awesome. Thank you @bernhard. Testing some things right now

I understand thats it's crucial to save bandwith. That's why we have webP now, finally. But there is one line in PagefileExtra.php that delivers the normal image url instead of the webp version, if the webp filesize is larger. In my case and I think on other sites too this is an unwanted behaviour, as quality and colors are different if you compare a jpg and a webp image. To illustrate this I attached this image, where you can see that the first three products which are being delivered as JPGs because the filesize is smaller are really different looking than the next 3 which are in webp format , especially in the logo area. This is somewhat hard to see here, but on my development site it looks really bad and is a showstopper for me to use webp. What I ask for is an option to skip the filesize check and maybe the option to enter a treshold value when to use the smaller image. I created a github issue "make the fallback optional if pagefile->url is smaller than webp" EDIT: This is already possible if you use following code: //_init.php // output webp version for all $image->url() calls, skip SVG's if($page->template != 'admin') { $wire->addHookAfter('Pageimage::url', function($event) { static $n = 0; if(++$n === 1) { if (strstr($event->object->filename, '.svg') === false){ $event->return = $event->object->webp()->url(false); } } $n--; }); }

What exactly do you mean with adding it with the API? Do you mean a file upload? Do you mean output? I think you are mixing input/upload and output here?!