kongondo

OK, didn't read about the MD part. Have you also edited your .js? For info though, here's how Wanze did it in ProcessBatcher.js /** * Setup fancybox for page edits */ var h = $(window).height()-65; var w = $(window).width() > 1150 ? 1150 : $(window).width()-100; $('.batcher_edit').fancybox({ type : 'iframe', frameWidth : w, frameHeight : h });}); In the above the class 'batcher_edit' does the trick (even without using the parameter &modal=1) in combination with the class 'iframe'

The link has to be given the class that will tell the javascript to open this in a modal. I have not used magnific but in fancybox in ProcessWire, I think the class was 'iframe'. Example code... "<a href='{$this->config->urls->admin}page/edit/?id={$test->id}' class='myClass iframe'>$test->title</a>"

@Vizz. Your site does not seem to be a ProcessWire website. I am moving this to 'Pub - Dev Talk for now. I am giving you the benefit of doubt that you are not a spammer . If you have any specific questions regarding ProcessWire please post in the appropriate forums. I've edited the topic title since it read like you are just advertising your own web development business (nothing wrong with that) but in the guise of asking a question. I have also deleted a link to your site.... for now...

Cool. Now you just need a Readme.md (you will eventually need this if you want to submit your module to the modules' directory. Then again, your module might just make it to the core(!) )

Blad, this looks sweet! Here's some resources to guide you regarding ProcessWire modules (naming conventions, etc.) http://processwire.com/api/modules/ https://processwire.com/talk/topic/2394-how-to-present-your-module/ https://processwire.com/talk/topic/741-a-guideline-for-module-naming/?p=6267

@Marinus, Thanks for testing Blog. Sorry for your pain in respect of manually removing leftovers. I personally don't like to remove leftovers manually! Before I get into details why that is an intentional feature, from your post I can observe that despite clear instructions in the first post in this thread as well as notes both in the GitHub project home and the module directory, and despite the fact that these are either typed in coloured or bold font, you did not (at least not entirely) read the instructions and/or notes . Just in case others miss them, this is what I am referring to: From the first post in this thread: From the modules directory and GitHub 'notes' sections. If you'd read the instructions and the notes, not uninstalling 'much' would not have come as a surprise .. Yes, I know my reason for not removing everything was not explicitly explained in the notes. Maybe I should add this to the first post but back to your question.... A module like Blog is a complex application. No matter how smart it is there is no way it can second-guess the various ways in which it will be used by the client. For instance, the module installs various fields. What if the user decided to reuse the Blog fields in their other templates? What if they decided to reuse some of the templates or add other code in the template files? What if they'd built their Blog content over time and down the road decided they no longer needed the full Blog experience but wanted to keep some or all of the Blog pages? If uninstalling Blog uninstalled everything.....well, you get the picture. This is something I thought long and hard about and also consulted on before making the call that "rather a painful manual uninstall than potentially destroying a user's data on uninstall!". . There's good news though..(OK, maybe not for you but others since you've already uninstalled Blog... )....... I already have a script that will remove all traces of Blog - fields, templates, template files, pages. The script was written before I released Blog. I was reluctant to post it but maybe now I should (as a Gist). I would like to package it better though rather than something that will run immediately the file is loaded. I am thinking of packaging this with prompts (are you sure you want to delete?!!), maybe even make it configurable to allow selection of what you want to remove from your current Blog install. Now that I mention this, I might follow up on an idea a friend suggested a while back. Maybe something for Blog 2.0 (if we ever get there ) - make the whole Blog install configurable - i.e. on install, the user decides what aspects of Blog they want to install. They don't want comments? Fine. They want to call Blog Posts 'News'? Fine, we can do that...etc, etc... Anyway, I hope I have answered your question somewhere in there UPDATE: Blog version 2 now removes its path of trash (rather than leave them behind ). It also allows you NOT to install commenting feature plus other stuff.

Blad, Nice effort. However, just wondering, how is this different from the grid view already available in ProcessWire image fields? Secondly, I am not sure this is a 'suitable' tutorial because you are editing/hacking a core file which is never good practice. It will get overwritten with upgrades. Edit: OK, so Adrian beat me. @Adrian scores are now tied at 1 - 1

You can add the file extension types you want in the array on line #35 of the code. $file_extensions = array('jpg', 'jpeg', 'gif', 'png'); Not getting this fully. You want to create a link where? Somewhere on the front end of your website or in the admin/backend? Drag and Drop: That's most likely a jQuery plugin. There's a number out there, I can't recommend any since I haven't used them. As for a thread about Soma's form, I can't recall seeing any. His blog post here might also be of some help RE flexible downloads.

I now have this (mr-fan's/first solution) permanently on my chrome's bookmarks bar aptly titled PW-GCSE (Get it? You see what I just did there? GCSE? ....Pete, Joss, Craig, help me out here fellas, pls ) https://processwire.com/talk/topic/7298-google-custom-search-for-your-browserbookmarks/

You only update something that needs updating . Eric Meyer's reset is still working fine for some people . Unlike CSS Frameworks, I doubt reset CSS change much over the years... Btw: http://www.cssreset.com/

It turned out to be a battle between 'normalizing' and 'resetting'. After reading up on (and testing) resetting versus normalizing (and because I am lazy), I decided to go with resetting (normalizing meant adding a few extra lines of code which I was not keen on ). I then decided to choose from what's popular out there and is HTML5 friendly. Ended up with html5doctor

HTML5 Reset Stylesheet http://html5doctor.com/html-5-reset-stylesheet/

Hi MidRo, Welcome to ProcessWire and the forums. I see your question has not been answered 7 days later! Apologies, we are normally not that slow RE spam, yes, a number of us (including Ryan) recommend using a 'honeypot' field to filter out spam. Read more here: https://processwire.com/talk/topic/960-comment-spam-filtering-alternatives/

OK, so that's external data, but what format is it in? CSV? SQL? other? I can't really tell from your sample But yes, it will have to be a custom script. Before that, you will have to map out the relations, create the receiving fields in PW, etc. There some examples in the forums (can't find them now) but others will chime in

Not quite following. Where are you importing from? Some external database? From within PW? If the former, batcher doesn't have such capabilities. if from within PW, meaning you want to add page fields to some template and then populate those page fields with existing PW pages, that can be done using the PW API using a custom script. How large is the data?

Aah, didn't know permissions work like that. If so, it is locked down OK...

Adrian, do you ever sleep? This is awesome man! Quick question, maybe I missed it, maybe this (especially with the new additions) should now be a superadmin 's only toy? Just wondering....

Doesn't sound right . No need to duplicate pages. Where an item can belong to more than 1 category, the 'normal' way is to create categories as separate pages, make them selectable in the items pages using a page reference field....This guy explains it better, have a read here instead: https://processwire.com/talk/topic/3579-tutorial-approaches-to-categorising-site-content/

@opalepatrick Not everyone knows of Soma's form-process.php. It would have been good to provide a link and/or some code. Secondly, if that link is a thread in the forums, then it would actually be better to post your question on that thread rather than start a whole new topic - it helps with context and continuity..

Nice one Brent! I am a sucker for soft subtle colours

At the end of the day, when it comes to public voting, I think such contests are really judging assessing popularity rather than 'best in its class' which is a rather more difficult and nuanced concept to assess. So if 10 people like/vote for Joomla and 2 like/vote for ProcessWire, does it mean that Joomla is 'better' than ProcessWire? Not necessarily. Does it mean that Joomla is more popular than ProcessWire? Probably.

Yeah, but remember this will only create one row, if that's what you want...Of course, that will be OK if you want to utilise the "automatic rows" feature

You won't regret it ....The Master himself uses it in his blog Same here. No more 'three columns small' stuff for me (no offence to other Grids out there )

Absolutely! You can change those. PocketGrid has only two classes; 'block-group' [which creates a row] and 'block' [which creates a column] . Have a look at the css file - it's only 43 lines long unminified ... The b1, etc you see on the demo site are custom classes to make it clearer what's going on. Edit: As you can see, it is very versatile and can be as semantic as you want (if you care about such things ). Btw, block and block-group can be applied to any element, not just <div>

Welcome to PW and the forums xporter. Nice to know that our documentation is great! Would Ryan's EventsFieldType be of help? http://mods.pw/5o - Not sure, maybe you'd have to extend it...