Leaderboard

Flourish for ProcessWire v0.9.0 ProcessWire wrapper around the great http://flourishlib.com'>unframework Flourish. This module has the same version as the framework, so whenever update happens, your http://modules.processwire.com/modules/modules-manager/'>Modules Manager will pick up new version and update the framework to latest version (if you're into that!). Happy hacking. Note: You should checkout the short module's code to see what I consider to be the cleanest approach on how to include other libraries/frameworks into your PW websites. Github: https://github.com/adamkiss/LibFlourish Modules directory: http://modules.processwire.com/modules/lib-flourish/

http://de.processwire.com/#support

It's very nice to see my figure on the website, but unfortunately I still don't speak German... I do say tschüß with a nice German tone though

Joss, I rewrote your script to actually work and did some refactoring. I think you'll live it. Let me know if it works. Here's the code: https://gist.github.com/somatonic/4743011 Which gives you this: <ul class='nav'> <li><a href='/'>Home</a></li> <li class='dropdown active'><a href='/about/' class="dropdown-toggle" data-toggle="dropdown">About 2</a> <ul class='dropdown-menu'> <li><a href='/about/what/'>Child page example 1</a></li> <li class='dropdown-submenu'><a href='/about/background/'>Child page example 2</a> <ul class='dropdown-menu'> <li><a href='/about/background/another-child-page/'>Another Child Page</a></li> <li><a href='/about/background/another-child-page-2/'>Another Child Page 2</a></li> <li><a href='/about/background/another-page/'>Another Page</a></li> </ul> </li> </ul> </li> <li class='dropdown'><a href='/templates/' class="dropdown-toggle" data-toggle="dropdown">Templates</a> <ul class='dropdown-menu'> <li><a href='/templates/asdasd/'>asdasd</a></li> </ul> </li> <li><a href='/site-map/'>Site Map</a></li> </ul>

I was planning to add something a bit more at once, but as there never seems to be enough time I decided to release what I had ready. Just pushed these minor improvements to GitHub. Version 1.11: Added: all field and template data shown + cached at template level Added: fields inside a fieldset are wrapped into a new subtree (page data only - fields inside a template are in a flat list)

Willyc speaks all languages.

ProcessWire is fast. With ProCache, ProcessWire is insanely fast! ProCache provides the ultimate performance for your website by completely bypassing PHP and MySQL and enabling your web server to deliver pages of your ProcessWire site as if they were static HTML files. The performance benefits are major and visible. Using ApacheBench with the homepage of the Skyscrapers site profile, we completed 500 requests (10 concurrent) to the homepage. The amount of time occupied to complete each of these was as follows: 29 seconds: no cache enabled 6 seconds: built-in cache enabled 0.017 seconds: ProCache enabled As you can see, the performance benefits are substantial. ProCache gives you the ability to drastically reduce server resources and exponentially increase the amount of traffic your server can handle. This is especially useful for traffic spikes. Beyond measurements, ProCache makes your website feel faster to users, respond faster to search spiders (which can help with SEO), and helps to conserve server resources for requests that actually need PHP and MySQL. ProcessWire is already very fast, and not everybody necessarily needs what ProCache delivers. But regardless of whether you need it or not, there is little doubt that you can benefit greatly from ProCache. For an example of ProCache in action, visit processwire.com or the skyscrapers site. Look in the lower right corner of the page (in the footer). If it says "ProCache", it means the page was delivered via ProCache. We did this for demonstration purposes (ProCache does not put anything in your markup unless you tell it to). More information about ProCache can be found on the ProCache documentation page. Please note There is a known issue when using ProCache with the LanguageLocalizedURL module. I hope to have this figured out soon, but for the moment you should not use ProCache in combination with that module as it doesn't appear to work in full. ProCache does not yet support multi-host capability (i.e. cache and delivery of different content per hostname), but it will very soon. How to get it Like with Form Builder, ProCache was produced as a commercial module to support development of ProcessWire. It is now available for purchase here. ProCache is in a beta test period. As a result, it's being offered with introductory pricing that may increase once we're out of that period. During the beta test period, I just ask that you let me know if you run into any bugs or issues during your use of ProCache. I also recommend that you follow the usual best practices with regard to backing up your site and testing everything before assuming it's all working. Beyond the introductory pricing, you may also use coupon code PWPC-BETA for 10% off the listed prices at checkout. This code will expire as soon as we're out of beta. When you get ProCache, you'll also get 1-year of access to the ProCache-members support and upgrades board, available here in the ProcessWire forums. Upgrades to ProCache will also be posted there for download. Disclaimer: At the date/time that I'm writing this, I think that I am currently the only one using ProCache in production use. That's why I'm providing it with the lower costs and coupon. If you are running production sites where everything must always work perfectly, you will either want to: 1) wait to install on important sites till it's out of beta; or 2) test thoroughly on a staging server or localhost before taking it to production use. In either case, always make sure you have good backups anywhere you install new modules, and always test to double check everything works how you want it to. Get ProCache Now ProCache Documentation Below are a few screenshots that show the configuration screens of ProCache. Have questions about ProCache? Please reply to this topic. Thanks for your interest in ProcessWire ProCache!

It took me a while tonight but I think I understand option "pages" now. The affordance for flowing checkboxes into multiple columns is the cherry on top. I want to buy someone a drink. I am *thrilled* with this software.

u must.added me.my name willyc jа.говорим немачки.добар willyc@prodigy.net http://williamc.com lisense id 39149538518 no.diseeses and pets.i no own

Also, shameless self-plug here: for even easier way to install, use & manage your Flourish install, checkout my new micro-module: http://processwire.com/talk/topic/2756-libflourish-%E2%80%93-flourish-auto-loader-for-processwire/

Hey Joss, this is great! Thank you.

As i said, i really don't like to give the costumers too much possibilities and try to avoid the WYSIWYG as much as possible - guess you all know why: ( Source: http://kopozky.net )

Great idea to build that site, Nico! Christian Schindler mediakreativ.de (very old homepage - no time to build a new one... )

Are you proposing rolling this editor setup into a Processwire collaborative module or something. Editing a Processwire page with something like that would make for some awesome app-like experience idea starters! Great find! -fanboy

Hi steve and welcome! Sounds like for some reason the Database Host is not recognized. Can you check those database settings in /site/config.php (at the bottom of the file): Is everything correct there? $config->dbHost = ''; $config->dbName = ''; $config->dbUser = ''; $config->dbPass = ''; $config->dbPort = '';

Maybe because you don't have "span" inside valid_elements?

Add the "style" attribute to the valid_elements table. Now you can set the width and it stays. TinyMCE converts the width="100%" to a style="width:100%", and since PW default config has "style" not in valid elements it gets stripped. Ryan, can could you add that "style" to the table elements or default @[id|class]? -- BTW you can also define classes to use with the table and I also always use the excellent html templates feature of TinyMCE to create various prepared tables that has the right settings to just fill in.

Interestingly, I was writing a script today with a client using Google docs, er, Drive. It was a bit of a fight editing exactly the same text at exactly the same time, but rather fun too! We ended up adding a skype connection so we could yell "stop doing that!" at each other.

Joshuag You might want to look at what I have done (er, am doing) with a bootstrap profile http://processwire.com/talk/topic/2411-bootwire-basic-twitter-bootstrap-profile/ Basically I am creating two - one that has bootstrap installed and then demonstration pages showing how some of the bootstrap elements work in this environment (which is actually straight out of the box, but it is nice to show it anyway) Then the second is the same things with just about everything removed - almost no fields, only a couple of template files, no content, just ready to go and put together so that more up-to-date bootstrap versions can be just dropped in place. The only extras in there is the standard Bootstrap menu system wired into PW and basic demo carousel and accordion files to save people having to mess around with these. So, that is the profile that is really useful to people - the first is just a reference. Joss

Stefan aus Freising - www.typneun.de

Stefan Wanzenried Bern, Schweiz @schtifu (someone has "stolen" my nickname, I joined too late...) everchanging.ch

Philipp Reiner - Heidenheim, Baden Würtemberg - @whysonervous oder eben "alte" Homepage philippreiner.info

hey!!

Philipp Urlich @somartist https://www.facebook.com/philipp.urlich

Matthias Mees - Eutin/Schleswig-Holstein - http://netzgestaltung.net Nico, if you need any help building that German site, translating or writing or whatever, just say the word.

Luis - Karlsruhe - misterui.de

Thanks Alan! Glad you are liking ProCache. I'm adding you to the ProCache board as soon as I finish writing this message. It is feasible to add it, and it sounds good, but there are some problems with doing this. It moves the render from one request to another. If a lot of pages were expired in the same request, it could even become quite a bottleneck on the server. The way it's setup now, the cache generation piggybacks on a page that's already being rendered, so it's very efficient and ProCache activities aren't ever going to consume all the server resources. Consider this scenario: a maintenance run expires 1000 cache files (a potentially common scenario on a large site)… if we have to regenerate them all right there (as opposed to when the page is next viewed) we will temporarily take over a lot of server resources… perhaps interrupting traffic to the site. Whereas, if we cache them on-demand (which is what it currently does), usage of those resources is spread out over a period of time, and generally focused on caching the most-important pages first. Even if we use cron to re-cache them incrementally, the use of resources would still be disconnected from the demand for them (i.e. caching pages that may not be needed in the short term while missing pages that are). But I understand where you are coming from. If you've got a page doing a lot of heavy lifting (perhaps taking several seconds to render) then you don't want any user to ever experience that. So I will put more thought into how such a situation could be handled. For now, if you want to limit the chances of users getting a non-cached page, the best strategy is to increase your expiration times and limit what gets cleared on page saves.

In a corporate environment I would strongly suggest not hosting the intranet on the same server as a public facing site. In addition you would want to secure the intranet behind a firewall in a DMZ and use a web application firewall like mod security as well. Also you would typically separate your DB from your HTTP server and pass those communications through a FW and VLAN with monitoring. Sounds like overkill? Check out the cost for a typical compromise. Happens every day. I don't know your environment, but the fastest attack path against / into a company is compromising a site/server that employees use. That is not to say the PW is a security issue, but that security should be layered. And as soon as you start serving up sensitive corporate data, the game changes. Just saying.

Joshua, I'd actually like to do a full HTML Kickstart profile for ProcessWire, if that'd be alright with you. Maybe we could collaborate on it sometime?

I am using Sublime rather than Aptana now - it is a memory hog issue (Aptana is huge) But I do miss some bits and pieces. Although I have the folder tree plugin, I miss the full file management you have in aptana - I cant copy and paste from Explorer into Sublime like you can with Aptana, for instance. Also, Aptana has a very powerful and built in syncing system that is much more full featured than the SFTP plugin for Sublime. I find I miss all the various additional reporting screens you get with Aptana/Eclipse much less than I thought I would. And Sublime is one hell of a lot faster - no typing lag (you get that with Aptana when you have a lot of projects). So, I will probably stick to Sublime now unless I am running on a very powerful box.

A nuisance with me though - I always have to wade through the list of errors I create myself; I don't need chrome adding to my woes.

Hi Ryan, just saw this now. We're working with someone now who found out about the job from this post. We're excited to be working with someone who's got solid PW skills. Thanks for the offer anyway. Should we ever come across any PW work that mere mortals can't solve, we'll be sure to reach out

Yeah, but I meant more like this because I'd forgotten about that second link : <?php // Some code to iterate through the folder structure needs to happen, but when we have a file we do something like this: $filecontents = file_get_contents('news2-sample.txt'); $filecontents = explode('<!--Head-->', $filecontents); // This splits your contents into an array containing stuff before and after the <!--Head--> delimiter $details = explode("\n", trim($contents[0])); // Now Package, Rank etc are in an array - $details[0] contains Package, Name would be $details[2] and so on // I'll ignore <!--FM--> as I have no idea what it is, so let's just imagine that wasn't in the text file $maincontent = explode('<!--Text-->', $filecontents[1]); // We're now dealing with things after the <!--Head--> tag. $maincontent[0] now stores the article title and $maincontent[1] is the body. ?> There's more you can do from there to turn the newlines in the article body into paragraphs but this gets you started with some ideas of how to parse it all. Someone will probably come up with a better way fo parsing it all using regexp though but I went with what worked inside my brain (regexp hurts my head too much).

I think I found the problem. It was just a TinyMCE thing. Uploaded a new version on GitHub. Should work...

I was actually thinking of adding a "Tools" menu to ProcessWire admin (in addition to Pages, Setup, Modules, Access). The reason for it is that we've now got a lot of tools that don't necessarily fit the definition of "Setup", so thought it might be handy to come bundled with another place like that. PW1 had such a Tools menu like this.

Thanks for sharing your experience. I stopped working on WordPress sites some time ago, but I offered to help a friend with his WordPress site recently and was surprised by how little had changed. That's rarely the case, but I did have a big client request WordPress once. They were very amenable to other suggestions though, as the work got rolling. Pretty soon the WordPress site was a thing of the past, and the character of the work changed toward a more flexible, powerful collection of tools and resources. Earlier this year I sat in a meeting with a client, across the table from a social media consultant who looked at me and said at one point, "we are using WordPress for this site, correct?" I was sort of shocked, but she didn't really know of any other software, and was used to using WP for everything. She is a bit frustrated that she has to re-train just to use a client's site, but what can I say...it's not like learning new stuff is some rare thing in our industry. This client would have been lost with WordPress. I'm even frustrated by MODx these days, so I must be turning into a real CMS snob. Just got a client's OK to move a large, fairly prominent MODx site to ProcessWire after I built a newer, smaller site in PW for them. So looking at my work, it'd almost seem that "the right tool" is always ProcessWire. But I think it's mostly that ProcessWire is a flexible tool that is well designed to solve common problems.

Hi, I have a small framework called HTML Kickstart. http://www.99lime.com