Leaderboard
Popular Content
Showing content with the highest reputation on 12/03/2024 in all areas
-
I really appreciate ProcessWire as an open source CMF/CMS. I have used it for 3 websites now. I understand that the Pro modules are a way to support the project, however I do not want to use any proprietary code because it feels like a backwards step; I like being able to use, bend, fix, study, share the software I use, and I actively contribute to dozens of such projects. Is there a way I can make a donation to the work of the project without buying a Pro module?4 points
-
Hello ProcessWire Community! I'm thrilled to announce that RockCommerce has finally arrived! Some years ago, after building a custom shop solution, I swore I would never create another ecommerce system again. 😅 Yet here we are! After months of hard work and completely rethinking my approach, I'm confident RockCommerce will be a game-changer for ProcessWire ecommerce. I can't wait to see what you'll create with it! 🚀 This video guides you through the Quickstart Tutorial, which was written by @Sanyaissues (THANK YOU SO MUCH!!!) He rose his hand when I asked for beta-testers 💪😎 He had never done E-Commerce before and wanted to understand how it works - so I sent him a copy of RockCommerce and let him play and this is what he came up with!!! Absolutely remarkable! Hat off to him! Docs & Download: https://www.baumrock.com/rockcommerce P.S.: To celebrate the RockCommerce release, I've applied discounts to all module licenses in my shop! If you've had a successful year, this is a great opportunity to invest in yourself and potentially reduce your taxes 😉4 points
-
Hello community, to my surprise and delight, my module “FrontendAutoReload”, which was previously only published on Github and used exclusively by me, was presented in the ProcessWire Weekly Newsletter #545. And because I haven't encountered any problems using it so far, I'm in the process of submitting it to the module repository. It's basically a little helper for ProcessWire template development, which automatically hits the refresh button in your browser each time a change in the template folder is detected. Not groundbreaking but a convienient timesafer. I would therefore be delighted if it could also be of some help to other developers. For information on how to use it, check out FrontentAutoReload on Github. If you have any questions, don't hesitate to ask them.1 point
-
You can also do this with the Pro modules. They are just PHP scripts like other modules. And you get access to the internal support forums of the corresponding pro modules. Of course you can also just buy the modules and not use them to support Ryan 😉1 point
-
Yepp! That's it. Now it works. Thank you Bernhard!1 point
-
Ok then it's likely because your PHP does not have the Intl extension installed. Please do that, then it should work!1 point
-
In most cases I would agree with you 🙂 but i think that it is a very special case that is adapted to our internal processes 🙂 However, it is often the case that users first ‘collect’ items in their cart and then order them together. Example: The user has a new mouse and keyboard in the ‘hardware cart’, but he knows that he would like to add a headset, but needs to find out more first. The purchasing department has announced a ‘collective order’ for company clothing, the employee would like to order something as well and therefore places the order for the clothing directly. There is also a specific shop where recurring weekly orders are placed (food), so this plays an even greater role here. But I think I'll have a look at the ‘partial checkout’ topic, I think that should be implementable 😉 Then only a single cart would be necessary.1 point
-
Many thanks @virtualgadjo and @AndZyk for your inputs. In fact I thought I would build my blog structure in a very simple manner, but both your input showed me, that thinking about structure is well worth!1 point
-
For the records: I found a way to use multiple points or areas directly from a repeater, but it's not the most beautiful method. It works by simply omitting the frontend part of the module. I just load the leaflet js and css manually, extract the lat and lng from the repeater, and paste them in the site. Which has the advantage that I can use additional fields in my repeater (in my example I use a field named "radius" to draw multiple circles: <div id="map" style="height: 200px"></div> <script> var map = L.map('map').setView([51.505, -0.09], 13); L.tileLayer('https://tile.openstreetmap.org/{z}/{x}/{y}.png').addTo(map); let boundaries = []; <?php foreach($page->my_repeater as $repeaterdata) { $diameter = $repeaterdata->radius * 1000; echo " var circle = L.circle([{$repeaterdata->map->lat}, {$repeaterdata->map->lng}], { color: 'red', fillColor: '#f03', fillOpacity: 0.5, radius: {$diameter} }).addTo(map); "; } ?> </script> Please note that this is just a proof of concept. I haven't played around with markerclusters, automatic boundaries or any other fancy stuff at this point.1 point
-
Ryan posted an (license) update on this in August 🙂1 point
-
@ryan, is there an update on this? It would be good to have PW use the current version of TinyMCE because v6 is now past the official End Of Life.1 point
-
3h after launch and we count the first extra wish 😅 Would you mind sharing the exact use case? The cart is at the moment tied to the user's session and there is one global cart for each user. It does not sound too easy to change that behaviour but if you tell me the exact use case we might find a solution.1 point
-
Hi @olivetree, my preferred structure is one template blog or news which contains children with the template post. Inside this tree I have two trees for categories and tags. Every post has two page references fields to reference one or multiple categories and tags. So it would look like this: Blog Post 1 Post 2 Post 3 ... Categories Category 1 Category 2 Category 3 ... Tags Tag 1 Tag 2 Tag 3 ... You could also use URL segments for shorter urls, f.e.: blog/categories/category1/ => blog/category1/ You can also enable a pagination or comments. Of course you can choose a different structure if you want to. 😀 Regards, Andreas1 point
-
If there is a new ProcessWire module in the wild @teppo will find it. Thank you for your module. 👍1 point
-
Hi, having made a few websites with blog/news or so parts, i would say that before chosing the way you'll do that with pw, there are a few question toi ask yourself first one, probably the most important one when it comes to structure, will your articles belong to only one category or will they be allowed to belong to more (as soon as it is two, think n 🙂 kind of a way of life, one is one, two is n 🙂 ) the second one, how do you want to - display the articles, lazy loading, pagination - select the article by category, isotope (or equivalent) or url segment - sub question, will you allow complex selections (articles belonging to more than one category at once, and so on...) once you know the answer to those little questions it will be far easier to decide you pages structure in pw and/or the kind of fields you'll need to categorize your blog articles, actually there is no limit in pw, the only one you could run into is something you hadn't thought about before deciding the structure 🙂 have a nice day1 point
-
@bernhard Problem solved (I hope) Cause: reference to RockMigration-json-file e.g. field rbp_text_text field rbp_text_text / tab 'Input' / 'Custom settings JSON' / 'JSON file' is refering to '/site/modules/RockMigrations/TinyMCE/text.json' I removed de reference ''/site/modules/RockMigrations/TinyMCE/text.json' + save Refresh site (F5) TinyMCE is visible Same positive result for the other blocks, accordion, features, ...1 point
-
Hey Ryan, thx for these additions! I'm wondering if there is a way to open a modal and then react/wait for something within that modal. For example we could maybe create an action for a page reference field to create a new page. When the page is successfully created in the modal and the modal is closed we could trigger the inputfield's reload event and the user could instantly select the newly created page.1 point