Leaderboard

This is an inputfield module integrating Trumbowyg WYSIWYG editor into ProcessWire, quickly hacked together after some discussion at the Redactor thread. Trumbowyg is a light-weight alternative to more feature-rich editors, such as CKEditor or TinyMCE. Both this module and Trumbowyg itself are still in alpha state. Customisation options include only a subset of what Trumbowyg provides, more will be added in the near future. Also, link and image features as seen in other RTE modules (TinyMCE and CKEditor) are not implemented yet. The module is available at https://github.com/teppokoivula/InputfieldTrumbowyg.

Hi rickm, This is recognized when images are resized. We want not to overwrite the original files with the GD-lib, because it would erase all metadata and even can modify the original image data significantly! So all variations created by ProcessWire are autoRotated correctly. If this doesn't work for you please check in your site/config.php the setting for config->ImageSizerOptions["autoRotation"]. (sent from mobile)

What you are trying to do is called Bootstrapping. You can easily bootstrap PW in other apps. Have a read here: http://processwire.com/api/include/ I don't know if you know this but you can also 'separate logic from content' by just using ProcessWire itself...PW is also a PHP framework not only a CMS. . There's also lots of posts about MVC around the forums...

Here is a website I nearly finished(Still waiting for decent photos from client for gallery) for a hairdresser in Slovakia so it's all in Slovak. http://www.milujsvojevlasy.sk/ This is the first site that I used profields. I used pro fields table on the price list page: http://www.milujsvojevlasy.sk/cennik/ Using Profields table made it really nice and simple for the client to update prices in the admin. For the booking system I integrated a separate script. Used my own grid system / framework http://www.cutegrids.com to make it responsive. and of course built using the fantastic Processwire and Profields.

Dude, you are on fire!

Ok. We just launched our new website today, of course now running on ProcessWire. A long journey with many iterations and somewhat experimental. Still a work in progress, as much as never finished. There's a lot of inter-linkage going on between content news, projects and competence pages. Modules worth mentioning: TextformatterAutoLinks Markup RSS Feed http://update.ch (IE < 9 not supported, sorry. Old Androids may experience strange things)

That was one of the best ones I could find of the hairdresser / owner. You should have seen the other ones. Let's say they were not for family viewing.

Here's the one I use all the time: https://processwire.com/talk/topic/497-email-obfuscator-module/?p=3897 ahh, sorry, that's the same link as yellowled posted

I haven't had any need for shop since the site I build it two (or was it three) years ago. That's one reason that shop hasn't got any love from my side. I build this paypal module since it was requested so many times. It should work just fine. I would like to build some of the components again, like better shopping cart, more general payment methods, independent checkout process etc, but not sure if I have time for it (especially since the need on e-commerce had been so little on my day job).

I just patched together some simple PHP code to scan for hooks: https://gist.github.com/owzim/6f7c2ef6394f25e04269 I think we could go from there and build a shell script that clones/pulls the PW repo checks out master and generates html > captain-hook-master.html checks out dev and generates html > captain-hook-dev.html updates the github page What do you think?

I would avoid putting it in /cache/HannaCode/. What does your include line look like? If your class file were placed in /site/templates/includes/ (for example) then your include line should look like this: require_once(wire('config')->paths->templates . "includes/YourClass.php");

I also ran into this issue and, in case someone else does too, it might be worth pointing out once again that this is not the value to change. At the end of the php.ini-file (that you find under the wamp-icon in the task-bar and then by in the menu picking PHP - php.ini) you have the xdebug lines. Just add the line... xdebug.max_nesting_level = 200 ...directly under the [xdebug]-line. After that, things should run smoothly.