Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/19/2023 in all areas

  1. I have just released the newest version 1.2.8 of AppApi. No breaking changes, but it should fix an issue that could lead to installation-errors when the used MariaDB version does not support JSON as db column type. Additionally I have included some bugfixes to the email-authentication logic.
    1 point
  2. @szabesz you are right, it's not considered as a bug (I might disagree), see https://github.com/processwire/processwire-issues/issues/1322 @saschapi I've forked tpr's repo and amended some changes, https://github.com/matjazpotocnik/FrontEndEditLightbox
    1 point
  3. @Macrura Hello Marc, Really, you're a champion ?? Anyone from a Joomla/Seblod content (and maybe others too) wishing to import content in bulk and being worried about the images, this is a lifesaver! This morning I updated PW to 3.0.212 and ImportExternalImages to 2.0.14. In the script to import the pictures after I imported the articles and all their fields I needed with ImportPagesCSV, I used the script hereunder (subject to be improved - Noobs will love you for this ? Maybe with a (total) img import counter as well at the end of the ride??) to monitor the process: <? $p = $pages->get(2356); $m = $modules->get('ImportExternalImages'); try { foreach($p->children as $c) { $c->of(false); echo "Saving child page: " . $c->title . "<br>"; $m->importImages($c); $c->save(); if($c->isChanged()) { echo "Child page " . $c->title . " was saved.";}} // didn't get the echo's though } catch (Exception $e) { echo $e->getMessage(); } ?> At one point during impot, in one of the articles, the img had a typo mistake of width="25ù" instead of width="25%" (Azerty keyboard key) and the import halted. When correcting the typo error in the article of which the title was reported thanks to the script, by refreshing the 'import' page the script went happily on importing pictures. At one point there was a timeout, but who cares ... I just refreshed page again and the module went on doing what it was supposed to do. Upon inspection, I couldn't help to be astonished as even the alignment of the pictures as in the original articles was maintained. Really: Hats off! ? Again, congratulations! Let this be a lifesaver to many people wishing to join the PW family! Kind regards, Bernard (temp overview https://kusttram.com/1325pw/overzicht-heemkundige-teksten/Pagina134 of a site in development without layout and temp pages - I will install dynamic search from @kongondo and from there seblod might be in the rear view mirror for many coming from the Joomla/Seblod setup - Here is the joomla/seblod combi I'm going to migrate from: https://www.zwinstreek.eu/geschiedenis/heemkundige-kringen/zoeken-in-publicaties?search=pdf&task=search )
    1 point
  4. This will be great for everybody using RockFrontend + LATTE. Thank you for your work and that update!! ? But there is still a small step missing/not working. I've added the explanation to the issue with screenshots demonstrating the problem. Would be great if you could take a look at that @ryan so that we can not only tick that request as completed but we can also actually use it to directly translate LATTE files in ProcessWire and we don't need the workaround any more ?
    1 point
  5. Great. It's an issue with ProcessWire if you put valid php comments in the "requires" portion of getModuleInfo() it breaks ? I'll create an issue for that, thx for reporting!
    1 point
  6. I originally developed and launched Real SF Properties in 2015 and did a complete design and programming refresh in 2022: https://realsfproperties.com/ The site was designed by BuzzCandy.Design: http://buzzcandy.design/ This was my first time using Tailwind CSS and it was a great fit for this project. I wish it existed back in 2015 because while UIkit has been my go-to CSS framework for several years now, there are some site designs (and designers) that I work with that simply need a higher level of precision to slice correctly and be maintainable. Sure, I could have used vanilla CSS and done it the classic way (separation of concerns), but Tailwind CSS and doing everything with utility classes (locality of behavior) does come with major benefits, even if the markup is not so easy on the eyes. This site does not use a matrix page builder or anything fancy. The sections are hardcoded but with the ability to add data using the various page data structures that feed in accordingly. It has also has an accessibility score that is extremely high. It's a quick loading site even though ProCache or CDN is not yet enabled. Other frontend libraries include Flickity and Headroom.js. More details on my personal website: https://jonathanlahijani.com/projects/real-sf-properties/
    1 point
×
×
  • Create New...