Leaderboard

Guys, I implemented sisyphus.js as a module. You can test it from here https://github.com/ocorreiododiogo/Local-data-saver-Processwire To test, edit one or more fields in a page and open that same page in a new tab without saving. The data should magically appear there I didn't test it thoroughly, so, proceed carefully. In this implementation, all changes will be saved to local storage until the from is submitted. after submission the local storage is cleaned. Ideal implementation would have a visual clue that the data was loaded from local storage, and not from the db, and would have a button to clean the local storage and replace it with the real data. PS: I can see some cases where this can cause confusion with multiple users, but currently it can also happen without the module.

Page Field Edit Links GitHub: https://github.com/thetuningspoon/AdminPageFieldEditLinks Direct Download: https://github.com/thetuningspoon/AdminPageFieldEditLinks/archive/master.zip This module is based on--and is the successor to--Macrura's AdminPageSelectEditLinks (https://processwire.com/talk/topic/8477-adminpageselecteditlinks-module-for-enabling-edit-links-on-multipage-selects/) Page Field Edit Links adds modal editing capability to ProcessWire's Page fields in the admin editor, allowing editors to easily view and edit the content of any page(s) that have been selected, as well as create new pages without leaving the current screen. Edit links are updated in real time when new pages are added to the field. Compatible with all available types of Inputfields including Select, SelectMultiple, Checkboxes, Radios, AsmSelect, PageListSelect, PageListSelectMultiple, and PageAutocomplete.

So today found a new strategy for building processwire website and it's more awesome than all the strategy in place, because it allows you to easy modify codes without bothering about appending to content or pre-pending to content, will write a tutorial about this. ever since i discovered wireRenderFile(), it made things easier for me. Will drop a tutorial soon, please keep this post in mind.

yes, it seems undeniable that AIOM+, which is otherwise a godsend plugin, has the possible side effect of tanking an entire website, front and backend, without warning. The cause is probably some change in the permissions, or who knows what; in my case the css minify was timing out in php, but had worked fine for a year before that. The module would seem to leave no recourse in the event that it fails and the developer has not taken steps as described above and in use by @muzzer and myself to provide an alternate way of outputting the assets. I think the module should come with instructions and warnings about these possible consequences, and that function i posted or one that does the same thing, should be part of the module so that if the user sets emergency shut off, it just lists the files in the arrays that have been passed into the class as single assets... it would also make sense for there to be a simple api for the module in the event that a site has tanked, to enable emergency shutoff; the api could also possibly allow for cache clearing, enable/disable dev mode and enable/disable html minify (this could also allow one to minify html or not on a per template basis, per horst's request..)

Earlier this week i noticed one of our sites (tools) had the following URL while working in the manager /processwire/page/edit/?id=1257390 Then i realized there where already more then 1.2 million pages, and processwire still running smoothly like a charm. I just wanted to share it here, and that i'm realy happy with ProcessWire. Thanks go to Ryan and all contributers for creating and maintaining this wonderfull piece of software!

So far I found it: wire/modules/Inputfields/InputfieldTinyMCE/InputfieldTinyMCE.js apply_source_formatting: true, Code inside Tiny MCE html source editor no longer looks like a blob of code but lined up vertically.

Fieldtype + Inputfield is also kinda common.

Nico, I'm having an issue you might want to take a look at: if the summary contains non-ASCII characters (in this case "ä" and "ö"), they seem to get stripped from the final file. Doesn't seem intentional. Another thing I noticed, and this is more a gotcha than a real bug, is the optional "implements" setting. It's true that "implements Module" can be disregarded if you're extending something that already implements Module or ConfigurableModule, but leaving it out unintentionally will result in weird errors, and currently the UI seems to suggest that this would be optional in all cases. This could be confusing, especially to beginners. Your default configuration options "+" UI made me wonder whether it would make sense to allow creating and bundling multiple module files at once? Most of my modules seem to actually consist of more than one module – a Process module for UI or API, another module for hooks, perhaps a third one for optional features, etc. This could be a border-case and would require some sensible server-side limits either way, so perhaps not worth the effort though. I'm also wondering if the source code for this tool is something you'd like to share and/or open-source. Not sure what your long-term plans here are, but I'd be happier if I could see how this thing works, perhaps report bugs and send PR's via GitHub, and just overall be sure that if something goes wrong I can have another copy of this very useful tool online (or installed locally for cases where I'm not connected to the Internet at all). .. and finally, I can't select ProcessWire 2.6 as "min. required PW version" yet For the record, I'm currently writing a paper that'll discuss module development in detail, and I'm very happy to be able to suggest this tool as the preferred method of setting things up. Of course I'll mention the "old-school" method of duplicating another module as a starting point (and even starting from the scratch), but IMHO your module generator has made other approaches obsolete in many cases

please disregard my question

I made a module back then... https://github.com/somatonic/AutoSave

Hi BernhardB - The "Show edit links?" option should appear at the bottom of the "Input" tab in the global settings for the field. I'm a bit confused when you say "page body field" since the body field would be typically associated with a textarea and not a Page field. Let me know if you are still having issues and I will look further into it.

Updated FU version 0.8.2 replaced hard coded verification email with simple html / plain templates to send an html email with wiremail. Has to be improved / changed in the future, but I don't know how I'll implement it (module configuration, template, ...) to keep it flexible and simple.

Welcome to the forum, mosid! Here is a discussion about RESTful API in PW where Ryan shares his thoughts about it. And there is Ryan's module Pages Web Service. I don't think it needs to be in the core. Thanks to PW's modular structure it is easy to implement.

Sorry to hear that There's nothing like writing in a offline editor and pasting it to the textarea for publishing. Or a browser extension like Horst said.

Had a strange and horrific experience on Thursday when a site i was working on suddenly could no longer create the new cache files...; i made a change to 1 line of a CSS file on the live site, and then that's when things went sideways. The CSS minify script started to fail and causing PHP timeouts, and then this took the whole site down, every page, and the admin. this is the error: 2015-05-09 18:49:28 guest **site-name** Error: Maximum execution time of 60 seconds exceeded (line 87 of /home/public_html/site/modules/AllInOneMinify/lib/cssmin.php) How I fixed it (for the moment): 1.) uninstall AIOM+ 2.) Replace with new copy 3.) Re-install it, and set on dev mode, no HTML minify. this thankfully fixed the issue, but all in all the site was down for quite a while during this, and it made me realize that this part of the chain in my websites is a weak link, especially if it can fail, in that the site cannot run without the css and js files. Typically I would always have $minifyCSS and $minifyJS vars in my _init.php which in this case i could have simply set to false and then no problem, i could have gone and fixed the AIOM+ issue while the site ran. But for this site I hadn't set that up yet and also I am using conditional loading and hadn't worked out the script to load the individual assets if one of those vars is false. After looking a bit at the module, i came up with this solution for disabling AIOM+ based on a boolean var in your init: if($minifyJS == true) { echo '<script type="text/javascript" src="' . AIOM::JS($jsfiles) . '"></script>'; } else { listAssets($jsfiles); } // END IF this is the function (may not be 100% perfect, still testing, but works ok so far): // use this to echo the assets in the AOIM+ array function listAssets($asset_files) { $templates = wire('config')->urls->templates; $current_page = wire('page'); // testing //$current_page = wire('pages')->get(1023); foreach ($asset_files as $asset_file) { if ( is_array($asset_file) AND isset($asset_file['loadOn']) AND isset($asset_file['files']) ) { $selector = $asset_file['loadOn']; if(!$current_page->is($selector)) continue; if(is_array($asset_file['files'])) { foreach ($asset_file['files'] as $_asset_file) { echo "<script src='{$templates}{$_asset_file}'></script>\n"; } } else { echo "<script src='{$templates}{$asset_file}'></script>\n"; } } else { echo "<script src='{$templates}{$asset_file}'></script>\n"; } } } In summary, i think that maybe there should be an emergency shut off in AIOM+, because without the method described above, how would you keep a site online say if AIOM+ was just totally failing?

Heads up for everyone, I just now updated the “stable” German language pack for 2.6.0, which – as usual by now – means a lot of work, mostly by Manfred, (translating all the things) followed by a little work by me (including a manual merge this time ). As usual, thanks to all the contributors, especially Manfred for his relentless efforts. Everyone, enjoy and please report anything you may find wrong or worth improving, ideally in a pull request at Edit: Yeah, URL would have been good, right? Report at https://github.com/yellowled/pw-lang-de, please.

Wow! Really awesome job there clsource. It really should be in processwire core as RESTful services is gaining attraction lately. What does ryan think about this?

Hi, everyone started somewhere. It's really easy once you have done it a few times. Check out this legendary post. Or use FormBuilder.