Leaderboard

NOGAJSKI FOTOGRAFIE I have relaunched my homepage. I don't remember exactly how many versions I may had since I launched my first homepage in 1999, but for me, the new one seems to be the cleanest and fastest. At least its the one with the best backend ever. (PW 2.6) The layout of all pages, including the slideshow, is usable from (300 x 260 px) up to bigger desktops (27''). I have tried to satisfy google PageSpeed, but only in a medium range. Other tools than googles do a more in depth analysis and show much better detailed results. But anyway. All pages uses one sitewide css file and one sitewide js file. Only the portfolio slideshow loads an additional js and css file too. (The server is setup to force browser caching, so with the second page view, no js or css dependencies need to be downloaded.) And ProCache is used! (what else) Besides my images API tools I use delayed output via Spex. CSS framework is pocket-grid and on the JS side I use LazySizes, Vegas and the new Photoswipe 4. Thats all. http://nogajski.de/ Here are some screens with minimal viewport (300x260): and here are two medium screens:

Hi guys, just finished new portfolio site. My friend Piter did the design, i did all the coding. In portfolio you can see couple of our sites, all build on processwire. Site is still in tests, so there might be some bugs . Cheers. http://avenueagency.eu/

ProcessWire is a tool that in most cases overperforms other similar softwares in many aspects. According to your actual project, PW may fit in or not. Even if not, I would recommend you to check for other solutions and use WP only if you have strong reasons (or your boss has, of course ). If your goal is to become a coding expert, WP is definitely NOT the way to go.

Hi, I use/wrote this little chunk: <?php class ProfileChunk extends \nw\DataProviders\ChunkDataProvider { public function populate() { $input = wire('input'); $user = wire('user'); $sanitizer = wire('sanitizer'); if (!$user->isLoggedin()) wire('session')->redirect('/'); $user->of(false); // check if they submitted a password change $passOld = substr($input->post->pass_old, 0, 50); $passNew = $input->post->pass_new; $passConfirm = $input->post->pass_confirm; // all three inputs have to be filled if (!empty($passOld) && !empty($passNew) && !empty($passConfirm)) { // check old password if ($user->pass->matches($passOld)) { if (strlen($passOld) < 6) { $this->message = ".. at least 6 characters .."; } else if ($passNew != $passConfirm) { $this->message = '.. passwords do not match ..'; } else { // everything is fine, save new password $user->pass = $passNew; } } else { $this->message = '.. the old password is incorrect ..'; } } // check and save other fields $this->message = '.. successfully saved ..'; $user->save(); $user->of(true); } }

Think you can use // authenticate returns true or false // ps: User is a user object if ($session->authenticate($user, $pass)) { echo 'yep password is the same'; }

i'd take this line from the hello world module.....so i think it will do the job. ....i wouldn't name this a "real" module...one simple hook and some configurationfields but with PW fortunately it is so simple... But it is a good exercise to start with easy tasks....and if i've luck we get a backlink from browser-update.org for PW! just looked into github....and found https://github.com/browser-update/browser-update/commit/9a781c48f7931d473be3bfaab4a61d12c9288da3

@BernhardB In this case checking for the template should be enough as everything you navigate to in the backend is most likely a process module with the admin template (I'm not aware of any exceptions). It's only if you call pages by the api where you need to check by has_parent. E.g. when you edit an user the users page is of the template user, but the rendered page is actually an admin template with the module ProcessUser running. So you're not accessing other templates directly, but through process modules.

You can simply answer that question. Files are uploaded via AJAX requests and then it's a matter of which file is finished faster. That has nothing to do with naming and I don't know if this "automatic sorting" could be changed. The AJAX requests most likely don't even know that other files are uploaded at the same time. What is doable is a sorting afterwards, either by javascript on user interaction (sort button) or with a module like I suggested above.

A highly configurable and flexible ACE editor input field. This module is sponsored in part by Nibiri, aka forum member Macrura which was a great jump start. So many thanks to him. See this short screencast to get an overview: Get it from Github or the Modules Directory. Roadmap add full screen mode expose a jQuery api for resizing, setting row count etc. add image handling like in Adam Kiss' version

This is my first module, and you can see how it started on this conversation http://processwire.c...0302#entry10302 It allows you to add images from an image field to any place of a text area by inserting this tag {fieldname:n}, where "fieldname" is the name of the image field, and "n" is the position of the image in this field. It will output markup on this format: <img src='$image->url' alt='$image->description'> To activate it on a text area field, go to the DETAILS tab on this field EDIT page, and choose it from the Text Formatters options. edit: on version 1.1 you can output all the images from one field at once by giving a 0(zero) index: {fieldname:0} IMPORTANT!: At the same time as I built this module, adamkiss started building a more robust module with the same functionality http://processwire.c...ld-tags-module/. We decided to merge efforts on his module so, possibly I won't work on updating this one anymore. I'll keep the download file in this thread for reference though. EDIT: created a GIT repo for this module. For downloading the module, head to: https://github.com/ocorreiododiogo/PW-ImageTags

Which is the one all the coolest kids are using? Yes, the coolest kids are you all, ProcessWired Friends. They've been around for a long time and I never was intrigued or interested in using either. I did some reading up and they sound pretty cool. What are you using? Why? Can you give me some newbie-advice?

https://github.com/ocorreiododiogo/pw-image-fields-markup http://modules.processwire.com/modules/textformatter-image-field-markup/ This is an old idea that I felt inspired to finish after reading this discussion https://processwire.com/talk/topic/9164-release-inputfield-ace-extended/?p=88717 This textformatter does more or less the same that my Image tags texformatter, but instead of using it's own tags, it tries to be completely agnostic while doing this, so you can use whatever method the markup language applied to that field uses. So, for example, If you are using Markdown on your that field, you would insert all images of a field called "images" on that page with:  or inserting the second image from the field called "images" with and alt text of "overriding alt text":  While for textile you would do this: !images:0! !images:2(overriding alt text)! As I said, this is language agnostic, so it should work with any markup language. The trick is to collect the images when they are already html img tags, and intervene only on those that are not urls by changing their attributes accordingly. I used the php native DOMdocument class for this. There are still things to be done, like targeting fields on other pages, defaulting to the first image field from that template and cleaning up a bit. But I'm not planning to do those at this point. Consider this beta.

So here i'm starting. This is more a little snippet than a whole module. On frontend before the </body> tag the script from http://browser-update.org/ is working - nothing fancy here. Download Github: https://github.com/mr-fan/MarkupBrowserUpdate my todo for this is: make it a clean module make use of the settings from browser-update.org so you could define these in PW backend get the backling for PW best regards mr-fan

https://processwire.com/talk/topic/10-how-do-i-interact-with-the-image-field-in-processwire/

Of course. That worked. Thank you so much, this saved me a whole lot of trouble. Greetings from Baden- Württemberg ;-)

Yeah, just scrolled down at a "reasonable" speed and noticed only 2 or 3 blank boxes, while before most of the boxes where empty.

You're mostly correct. About the WP Loop comes this to my mind: http://www.designer-daily.com/wp-content/uploads/2012/08/query_functions.jpg. ProcessWire simple uses php functions like foreach, implode, explode and since a few versions special convenience functions WireArray::implode & WireArray::explode, which work similar to their php counterparts but look a little cleaner. No need for a strange loop object if you can simply iterate everything thats at least array like or even an array. Regarding the calendar / ecommerce thing. It's true that there aren't many ready made plugins out there, but at least for ecommerce it may even be better to use a dedicated ecommerce cms.

Sure, I don't want to invalidate this, but the perceived feel of speed is totally drawn away by those empty boxes. Especially if I compare that to how my photography website loads on second visits. It's a blink and the images are there. I totally see why one wouldn't want to load all images before they are actually visible, but on the other hand why wait for loading images if it's not blocking anything. All other things which load initially are available in a breeze.

Very fast, even with such number of images! In Chrome (39) the main menu doesn't always stick to the top but scrolls with the page. If I add this to "header#hnHeader", it seems to fix it: -webkit-backface-visibility: hidden; backface-visibility: hidden;

While the pages are quite fast I noticed that I get a lot of "blank" image containers initially and on every page load. Seems like lazy-loading prevents cached images from being displayed, as they display quite fast as soon as I stop scrolling. For this few images I would really think if it's worth to have lazy loading for the thumbs. These blank containers really make the loading feel slow here, even though it's the opposite.

Damn, that loads quick ! Pages are switched before the links are clicked.

Hi, i noticed on my sites and also on other processwire sites, that the time to the first byte is quite long (> 500ms). Is there a way to speed up this waiting time, without using plugins like ProCache? i benchmarked some sites from the showcase and from Processwire weekly and nearly all of them perform bad at First Byte Time. is this related to Processwire or just standard behaviour for php/cms sites? Here are the tests: First Byte Time - Grade F URL: http://c-logistic.de/ Test: http://www.webpagetest.org/result/150601_J7_3992e9491b6acf72f73f10441880e6a2/ URL: http://von-bergh.de/ Test: http://www.webpagetest.org/result/150601_8S_cc7abdaa6519aae4904ea067ca5adf3c/ URL: http://www.canton.de/ Test: http://www.webpagetest.org/result/150601_7S_a8d3c3cf3d4f8ad2c3d3048a31864c81/ URL: https://www.maletschek.at/ Test: http://www.webpagetest.org/result/150601_42_8379a987c81ee2b8aa11f50b7a74694c/ URL: http://www.deichtorhallen25.de/ Test: http://www.webpagetest.org/result/150601_SS_90b428db03a86a5a309bd80aec294706/ URL: http://www.orkork.de/ Test: http://www.webpagetest.org/result/150601_VJ_63b76ec1ab9f37a93b9776320059a0a6/ URL: http://www.dojofuckingyeah.de/ Test: http://www.webpagetest.org/result/150601_J5_db3c199ddb74cfae513bbbe775b947c8/ URL: http://www.schloss-marienburg.de/ Test: http://www.webpagetest.org/result/150601_KY_01db3003b66dfad3b91aa40cbfda8f82/ First Byte Time - Grade C URL: http://www.grupoolmos.com/ Test: http://www.webpagetest.org/result/150601_ZH_8b9a2af518a9ac0cb30130e2aa3d3f2d/ URL: http://www.pipistrello.ch/ Test: http://www.webpagetest.org/result/150601_RK_5cf4d97c7fe1d4db3a145c565a84069f/ URL: http://transformationswerk.de/ Test: http://www.webpagetest.org/result/150601_9D_f16e00a262ec9d30b19ff67a290216ca/ URL: http://transformationswerk.de/ Test: http://www.webpagetest.org/result/150601_9D_f16e00a262ec9d30b19ff67a290216ca/ First Byte Time - Grade B URL: http://brakhax2.com/ Test: http://www.webpagetest.org/result/150601_JE_6552783547f8f7b73945a4698af8f231/ First Byte Time - Grade A URL: http://www.1815.ch/ Test: http://www.webpagetest.org/result/150601_Z5_f97b31533f61453aaeefc6cafef20e83/ URL: http://new.korona-licht.de/ Test: http://www.webpagetest.org/result/150601_RD_37ece6079e30ff5858c95db932f91e30/ URL: http://processwire.com Test: http://www.webpagetest.org/result/150601_V0_c812f846f6555e506fbd2b8ba9efe2e6/ Thanks!

They are essentially the same. The latter one is just a convenience function which does also just use php's count().

These sound very much like ckeditor specific issues. That thing isn't really meant to build whole galleries of images, but to manage text / image content. You would maybe have a better time rendering the images with the api in an automated fashion.

2.5.3 is not the latest version. We're at 2.6.1 for the stable release, where this bug is fixed. If for some reason you don't want to update the installation, which I would much rather suggest, you could also try to recreate the field and set it up with disabled multi-language descriptions before adding anything to it. As soon as an image is added before this setting was enabled it's never going back to using a single description.

I posted an PR which fixes the issue. Currently the core doesn't save the string value before checking by "title" and overwriting the string. The next check for possible "value" matches failed therefore. https://github.com/ryancramerdesign/ProcessWire/pull/1226

congratulations for your first real module - mine is still waiting one thing to this line: https://github.com/mr-fan/MarkupBrowserUpdate/blob/master/MarkupBrowserUpdate.module#L132 https://processwire.com/talk/topic/10106-api-problems-with-implementing-search/

Well, I realized that another approach (using PageTable) was actually more suitable for my specific needs, so I did not dig any deeper into the above issue. I believe it has been brought up somewhere in the ProFields support area, though.

I think you didn't understand what I tried to describe. HTML attributes are two parts: attribute="value". You can only allow predefined values for classes and styles ( with () and {}). You cannot do that for other attributes, like in your case id. You can only allow the whole attribute without restricting the value. *[id] (id in literally these two characters, not as replacement) does allow id's for any element and any actual id value. Kinda like this: <* id="*"></*>

I don't know if you read the documentation for "Allowed Content Rules", but there it states that [] are for attributes, {} for styles and () for classes. Therefore you need to use *[id] to allow id's. You can only allow/disallow specific contents for the style and class attribute. All the other attributes (including id) are either allowed in any form or not. Edit: Your version would allow for this: <a centre="something" gras="green" noir="dark" credit="given">I'm a link</a>

I can write a book on why i don't use Wordpress i wrote a long rant on it in a forum before, I am thinking of writing an article, however i do have some fears, so many Wordpress Ninjas and goons around me.

The same with Domainfactory (http://df.eu)

Guys, this thread gave me the impulse I needed to finish an idea that I started long ago. So, here is a new module for using image fields inside textarea using the same markup language that you are using in that same text area https://github.com/ocorreiododiogo/pw-image-fields-markup edit: still testing and work in progress, so I'm not submitting to the directory yet

arjen, did not know of this feature, looks great. Added it to the roadmap. To all: Feature requests and bug reports very welcome!

Really looking forward to experiment with this! I always liked ACE since I use Textile a lot. I've seen the roadmap and full screen would be awesome. Another thing you might consider is image handling. Something like this done by Adam. Thanks and great work.

The only thing remotely like your wish is the InputfieldPageAutocomplete. It's in the core but by default it's not enabled. It's like the PageListSelectMultiple, but instead of a pagetree you've only a autocomplete textfield to add pages to the field. Edit: You can take a look at it here: http://modules.processwire.com/modules/inputfield-page-autocomplete/