Leaderboard

The latest 99Lime website, http://www.yucatanliving.com. Everything you ever wanted to know about living and experiencing life in the Yucatan. This was a huge project with a ton of different sections and templates. With Processwire we created a very large site with a lot of different content types and information without making the administration complex. We are very happy with how this project turned out and our clients love it! Processwire rocks the casbah! Shoutout to: Orlando world's most awesome processwire dev. Notable features Galleries Categories Search Advertising page /es Getting started 100% responsive Polls Event lists Custom Calendar of Events Module Custom Advertising Modules 404 Dynamic CSS colors Users and profiles. A few details. Over 1600 articles 20 templates A ton of Fields HTML KickStart jQuery Custom roles ProcessWire Modules used Custom CRON Module FieldTypeColorPicker FieldTypeConcat FieldTypeFontIconPicker Map Marker ProFields FieldTypePoll FieldTypeSelect Form Builder Migrator WordPress Migrator Batcher JumpLinks Comments Manager ListerPro New Comments System Video embed for YouTube/Vimeo Custom-built Advertising platform module. Custom-built Recurring Calendar module. Jquery Modules used Remodal ImageLightbox Sticky-kit BxSlider FitVids Jquery-Touch-Swipe-Drag

I think most of your issues are gone when you understand a little more about processwire. I would suggest to install a 'play install' where you can mess around and are allowed to break anything without issues. Especially take a look at permissions and roles and all template settings. 1. New pages. solution: Set your family settings right in the admin. 2. Overview. Again family settings & give examples and explanation at field level. 3. Clutter in the tree structure. Put settings in /processwire/settings/ folder (Don't forget te set access for settings folder) 4. User error risks. Setup proper permissions and it's solved. 1. Buttons. Already there (parental relation in template settings) PS: How do I create "apps" nav items a left menu (example)? Create a page under /processwire/

I have observed clients having issues knowing which "New" button to use, but I'm not sure how this could be made more intuitive. It would be interesting to hear some different ideas. That said, the page tree is very intuitive, in my opinion. Most CMSs require you to do a two step process: create a page in some sort of massive "content bin" and then create a menu item that links to it. Usually the interface for creating the item is far less elegant than PW's page tree. In my experience, PW is a breath of fresh air for clients. You do have to put in some effort if you want to make the experience as seamless for clients as possible. In my opinion, the "Family" settings for templates is not optional. You really need to put the time in to set these-- Clients shouldn't be able to create a blog entry or news article outside of the blog or news section. That's just asking for trouble! Also, you can do a lot by setting access/permissions on your templates. You can prevent certain pages from being modified, while still allowing access to modify their children by giving the child templates different access settings. You can also lock pages. I really recommend playing around with some of these settings and logging in with your editor permissions to test them out until you get things fool-proof.

http://modules.processwire.com/modules/inputfield-textarea-markup/

The value is meant to be use for the html value attribute, therefore markup has to be striped. Use $field->label and $field->label2 to change the texts around the checkbox.

Quickly toggle your checkboxes with extra action buttons via AJAX. The module adds functionality to InputfieldCheckbox so you can toggle the checkbox fields in the extra action buttons intruduced in ProcessWire 2.6.5 via AJAX. Github Page Download Link Requirements This module works only for ProcessWire versions later than 2.6.5. How to Install 1. Copy the files to /site/modules/ProcessQuickToggle/ 2. In your admin, go to Modules > Refresh for new modules. 3. Click the "Install" button next to "Process Quick Toggle". Usage Go to any checkbox field you want to enable quick toggle feature for. Setup > Fields > my_checkbox_field. There in the Input tab you should see an Enable Quick Toggle field. After you check it you will see some fields that you can fill based on your needs. Then save the field. Now there should be an extra button for every page that has this field in the Pages tree. Features Supports template contexts. Supports core FontAwesome icons. Any kind of feedback is appreciated.

Huge site man, nice work! Looks like a ton of sweat and tears. I noticed that you have HTML tags in some meta-tags, which at least W3C and Chrome doesn't like. For example on this site: http://www.yucatanliving.com/art/mayaland-stained-glass-windows <meta name="description" content="If you are going to Chichen Itza, consider walking out the back entrance towards <a href="http://www.mayaland.com/">Mayaland </a>(or driving around and parking there) to check out these beautiful stained glass windows..." /> Same in the og:description-meta. If you don't mind some criticism: one thing that really bugs me is the navigation. I feel a little lost with all those links, which don't seem to be structured in any way (or I just didn't get it ). I just don't feel 'guided', hope you know what I mean. Cheers

Hey, so after having used the Fieldtype Select for a few project I had some customers that wanted a radio version of this so I decided to modify it (not heavily) and make it work with radio buttons instead. I have it hosted up on github here so check it out and let me know if you have question or comments.

@quickjeff, Found a bit of time to work on this. The Authors' Dashboard was also relatively slow. Worked on that as well. Using a combination of $pages->count() (thanks @adrian) and raw SQL queries (as explained here) and testing using 10,011 posts, the main Dashboard loads in 0.3 seconds on my machine. I think that's an acceptable time (given the 10+ seconds it took me to load main Dashboard with 5K posts). Although I tested with a minimal comments count, I don't think this will make much difference where there's lots of comments (using SQL for the counts). I will also look at Categories and Tags (in cases where these could run into thousands) just to be sure. Posts Dashboard loads fast as usual. Unfortunately, I still don't have time to merge the new changes any time soon.

You can just edit the first post and choose "Use Full Editor" to edit the topic title.

// Should be automatically sorted like the page-table field. $page->pt_contents->get("template=part_text");

no problem, your suggestion to do it by a new inputfield-file variant works perfect, i have a multiple-file field now, that executes the imagick scaling after upload und shows the generated thumbnail in the file-list. pretty good for the first step, as i think.

Thanks alot Horst for your time! The lines are hardly visible so not sure. These indized optimized png's I attached do have these lines when resized. When I do convert such an image to normal rgb png and upload it these lines are still there. Now It seems that it depends on the Photoshop version! I'm not sure how, but a png from a coworker saved in CS6 seems to work and has no lines. it's also when I open the optimized pngs in my CS4 the alpha transparency isn't shown and the modus is indized 8bit and the transparent shadow is black pixled, while in CS6 it shows the png correct as rgb and alpha transparency. The agency that does the images sent us unoptimized pngs and they seems to work.

Thanks a lot, Mike!

Thank you! That’s it. I should read the cheat sheet more conscientiously. In combination with adding an additional hook before the $pages->save it works like a charm. Pull request for module version 1.2.1 is already out: https://github.com/formmailer/SchedulePages/pull/9

I would also like to add to what thetuningspoon posted. The bigest problem that I have observed with develpopeing any application is where users not knowledgeable in the technology request more and more 'one-click' solutions to the tasks they wish to perform. I'm not knocking these users at all -- We all started with no understanding (and we should never forget that). I personally, however, do not think it is the correct approach to modify PW in this manner. It is a framework upon which we as developers build an application, and subsequently a simple-to-use interface. I only ever intend to expose the PW administration to any of my clients that are qualified, otherwise, I will construct an interface for them to use. As developers, our target audiences have a wide range of skills; from no skill at all, to the skill levels seen from the members of this forum (excluding myself). Although PW is presented as usuable by skill levels between this range, I think the responsibility lies with the user to learn the platform we recommend (assuming we pick the platform that best fits their capability and functional requirements). If they are unable or unwilling, then they might want to stick with - *shudder* - wordpress. Being new to ProcessWire myself, I am learning more and more about its capabilities, and my capabilities using it, as my framework of choice. Does PW fit every requirement? Of course not. But, in my humble opinion, it is the most robust and developer-friendly CMF I have found.

Martjin was faster while I'm fighting with my touch screen....:-( Just ask exactly your usecases with a good description and there will be a solution ....the administration interface from pw is just API and pages like everything else...

Just short from mobile....;-) Processors provide all option to create a simple user interface....build for every specific project separate.... Just some points on this to search some reading stufff...may I link it later.. - family tab settings - template permissions - make intensive use of the "add new" button....my clients log in after two months and click just....add new select article/page/document... - even create a simple administration dashboard is easy like creating a template for the backend....there are some modules on this topic... - its even possible to change the process of the "pagelisttree" to use Lister pro module ......much more option on this and every turn is on the one who use and setup the system for the client.... ;-) Regards mr-fan

Set a cookie and check if present. I would do it JS only.

Redirects does not support wildcards, which is why Jumplinks was created. In your case (I assume your intention here is to drop the .html extension from all requests), you would create a jumplink like so: Source: {all}.html Destination: {all}/ Alternatively, you can ask Jumplinks to check common extensions (such as .php, .htm, .aspx, etc.) by using the {ext} wildcard: Source: {all}.{ext} Have a look at the Wildcards and Smart Wildcards documentation pages for more information. If you would prefer to use mod_rewrite, then you can use this as the very first rule, just after RewriteEngine On: RewriteRule ^(.*).html$ /$1/ [R=301,L]

I am going to chime in and say that isn't really correct There are lots of acceptable ways to do something, but even as brilliantly thought out and architected as PW is, it doesn't prevent you from writing template code that results in slow/inefficient queries and also potentially dangerous holes that users could exploit. Keep in mind that there isn't any CMS out there that can prevent you from making these mistakes. PW makes it easy to do it the RIGHT WAY, but you still have to think things through, follow best practices, and if in doubt ask someone more experienced if you are doing it right, or at least make sure you are not doing it wrong!

Remember: There are MANY ways to do something with ProcessWire. One way will have 20 lines, then you share your code, and someone else will modify your code down to 10 lines, lol. There is no WRONG WAY.

want to say many thanks to @thetuningspoon for putting this together, and doing all the work of submitting to the directory. It's surely a useful module (use it almost every site), and we hope that all y'all will like it..

Please excuse me for referring to myself: discussed "a zillion times" ... This sentence should become part of the forum rules. Maybe some of you know the funny story written by Paul Watzlawick in "The Situation Is Hopeless, But Not Serious: The Pursuit of Unhappiness"? A guy is seeking for his lost keys under a lantern but can't find. Asked if he lost it under the lantern he replies: "No, I lost it somewhere else, but only here is enough light to find it."

ProcessWire IS successful. I've not read all but think it's all kinda way off to what PW is in its philosophy and core. Sorry, but I usually am too lazy to read more than 2-3 paragraphs. You need to work on your end-user usability (me reading your post, or not).

TextformatterThinspace is a trivial text formatter that removes repeated spaces (either ascii or non-breaking) and repeated newlines, replacing them with just a single instance.

Another option that would bypass Pw caching, even ProCache is to send an ajax request to handle the counter. If you use jQuery, this would be something like this: //Javascript <script> $(document).ready(function() { var data = {'action' : 'handleCounter'}; var url = '<?= $page->url?>'; $.post(url, data); }); </script> //PHP if ($config->ajax && $input->post->action == 'handleCounter') { //... //put your php code in here //... exit(); //Quit since this was only a request to update the counter } To make this work you would need to disable caching for the POST "action" variable. This is done in the template settings under Cache > Cache disabling POST variables