Leaderboard

Hello ProcessWire Community, It is with great pleasure that I share with you the new site for our company Strangeloop Studios, a visual design lab and animation studio based in Los Angeles. We specialize in content for musical artists but have branched into VR, Broadcast, and Music Video projects as well. This is my first site using ProcessWire. I went from complete PW beginner (October 2022) to this re-design and catalog of our various projects in the space of several months. Lurking here on the forums and visiting all of the stellar work that gets shared on the Showcases has taught me a lot. Many thanks to @bernhard for the Rockfrontend module, and @flydev for their Duplicator module. I probably wouldn't have been able to get this far without those … so, many thanks for your contributions! I also appreciate the feedback to my questions in the forums from several users who have improved my understanding of PW with detailed explanations. Things I would like to improve: optimizations for image delivery Multi-language support Looking forward to building more with ProcessWire! Cheers,

This week we've got ProcessWire 3.0.211 on the dev branch. Relative to the current main/master version (3.0.210), this version is 20 commits ahead. Many of the additions are user-submitted pull requests, and there are also several minor issue fixes too. Full details can be found in the dev branch commit log. I'd been planning on merging InputfieldTinyMCE into the core on the dev branch almost right away, but with so many minor fixes and improvements being added (that don't need much testing) we may put out another main/master version first in the short term, and then merge in InputfieldTinyMCE. Thanks for reading and have a great weekend!

Hi @benbyf Maybe this module does help you too:

I created a GitHub issue: https://github.com/processwire/processwire-issues/issues/1669

$wire->addHookBefore("Inputfield(name=roles)::render", function (HookEvent $event) { $field = $event->object; $field->appendMarkup = " <div class='uk-margin'> <button class='ui-button' data-options='1'>Options 1</button> <button class='ui-button' data-options='2'>Options 2</button> </div> <script> $(document).on('click', '[data-options]', function(e) { e.preventDefault(); let options = $(e.target).data('options'); if(options == '1') { $('input[value=37]').prop('checked', true); $('input[value=38]').prop('checked', false); } else if(options == '2') { $('input[value=37]').prop('checked', false); $('input[value=38]').prop('checked', true); } }); </script> "; }); Just adjust name=roles to name=your_options_field and value=37/38 to value=your_option_id (inspect via devtools) Have fun ?

The computer mostly did a good job, but I wouldn’t put it quite like this. One major thing to note about ImageMagick is that it is generally used without a graphical user interface and in fact without immediate user input. If the server on which you run ProcessWire has ImageMagick installed, ProcessWire can use it to create versions of your images in different sizes such as thumbnails. Shared hosting providers sometimes offer this (some don’t, but ProcessWire can also use a different library called “GD”). Basically you wouldn’t manually use ImageMagick before uploading images to your site. FileZilla can be used to install ProcessWire and transfer your own PHP code, but for uploading images and managing your webcomic, you would use ProcessWire’s admin area. That is, you would upload images over HTTP instead of FTP. ProcessWire then automatically creates thumbnails and puts everything where it needs to be (on the file system and in the database). To do this as a user you don’t need to know what any of these things mean. You just click upload, choose your images and hit save.

Same for me. Encounter a problem. Search the forum, and find an answer that I provided myself ?

Your question doesn't make sense. I thought it a good test case for ChatGPT. Here's the AI's answer: Webcomic Site Software Comparison Would ImageMagick work good for a webcomic site or is FileZilla the better option? How do they work and what’s the pros and cons of them? ImageMagick and FileZilla are two different types of software. ImageMagick is an image manipulation program, while FileZilla is a file transfer protocol (FTP) client. ImageMagick can be used to process and manipulate images, such as resizing, cropping, and converting file formats. It can be useful for a webcomic site if you need to process and edit images before uploading them to the site. FileZilla, on the other hand, is used to transfer files between a local computer and a server. It is a popular FTP client that can be used to upload files to a web server. FileZilla would be useful for uploading webcomic images to a website or web server. The main advantage of ImageMagick is its ability to process and manipulate images, which can save time and effort when creating and uploading webcomics. The main advantage of FileZilla is its ease of use and reliability when uploading files to a server. In summary, ImageMagick is an image manipulation tool, while FileZilla is a file transfer tool, both of them can be useful for a webcomic site, but for different purposes. The choice will depend on the specific requirements of your webcomic site.

Hi @virtualgadjo - it's only one language at a time IIRC. The problem with multiple is how to arrange the data in the export. Different users will need different layouts so it's best to generate these sorts of exports yourself. I tend to use AdminActions to create these sorts of custom imports.

Sure, done! Thx for the input ?

Ha just had another case today where I needed this and forgot I'd already worked it out once nearly a year ago ? This happens to everyone right? ?

@gebeer Every block gets wrapped by an element. The default is a "<div>", but the wrapping element can be changed to something else than div. See here. You can even let users change the element tag in the Style Panel. (Note: The markup inside the wrapping element is based on the template file the developer created in the "site/templates/blocks" folder). For me using "<div>" as an element for layout/design seems semantically fine. Divs are defined to not convey any meaning (i.e. they don't alter the "structure" of the document). Actually a lot of (CSS) frameworks and websites are build like this. Having those HTML5 tags like article, section, nav, etc. inside divs. But yes you can change it ?