Leaderboard

This week’s core version on the dev branch includes a lot of small fixes and improvements. We’ve also got a new multi-language URL field available this week as well. https://processwire.com/blog/posts/processwire-3.0.65-core-updates/

Hi, and welcome to ProcessWire! ProcessWire uses a separation of concerns approach, where the backend is completely independent of the frontend. As such, the frontend is not considered a theme, as it is not integrated with the backend in any way (by default) -- this gives designers complete flexibility to define every aspect of their site. Each Page (be it in the root of the Page Tree, or a child Page) maps to a Template (Setup > Templates, and each Page-Template assignment can be found under the Page's Settings tab), which maps to a Template File (/path/to/site/templates/). Each Template defines what fields pages allocated to it will use. So a "Basic" Template could have "Title" and "Body", and any pages that use the "Basic" Template would have those fields. In terms of a hierarchy, Pages can be moved to any location in the tree. When you move a Page, it simply changes the effective URL and physical location in the tree. It does not change how the Page itself is presented, as the Template and Template File would still be assigned. Regarding alternative text, that would depend on how the template builds your page. If the image in question is set in the actual Page editor, then you would be able to change the alternative text there. If it is set explicitly in the Template File for that Page and associated Template, then you would need to change it directly in the Template File. So, for us to answer this question in more detail, we would need to know a little more about the site in question. I've given a brief outline above, even though your question could do with a little more clarity. If I haven't covered something (perhaps more specific) that you need to know, please let me know. Once you get the grip of ProcessWire, it's simply impossible to look back - WordPress looks very limited in comparison when you start to understand the power of ProcessWire.

I'm not really sure if it's worth the hassle to care for own servers' email reputation. Especially when running on a shared hoster or any cloud service your ip is shared with others – on cloud services some other customer might have had the ip before yourself – so the reputation is not only in your own hands. And even if that' not the case it might be easier to pay a service than to spend hours trying to get to the cause of the bounces.

Look here

Maybe this can help too https://www.tawk.to/

There's no reference, it's a normal page. The only reference is the pagetable field itself. Ring a bell? $thepage = $pages->get("template=basic-page, mypagetable=$page");

Just working on some smaller projects and take the step into the actual master/dev version and all the new methods and api chunks that are coming with the 3.x series... since i'm not always build websites i'm not always go with the brand new things and put them in my workflow....there is a 24 per day timelimit i think...;) BUT actual i dive deep in markup regions....and holy shit this feature ROCKS! It should put in place better than in some blogposts: http://processwire.com/blog/posts/processwire-3.0.49-introduces-a-new-template-file-strategy/ http://processwire.com/blog/posts/processwire-3.0.62-and-more-on-markup-regions/ or can some admins make a headline in the official docs and link to the blogentries?? This feature is to important to get missed for beginners and other users of PW! I'm just kick my whole workflow and change it for the markup regions....i'm feeling like xmas in summer Thank you @ryan Best regards and happy "new" year....

I have been working on regular repeater support, but it's not quite there. The current problem is that the event object is taking its data from the parent page, in the case of a repeater, it's the repeater page (not what we want). So I have to do a bit more work detecting if it's in a repeater and use getForPage() to populate the event object. A couple other little details. Getting close, but still not there. It's coming though!

Thanks, I'll check them. I meant that magicline is removed by default by PW, you will need to edit the field in question, and on its Input tab go to the bottom and under Remove Plugins delete "magicline" text.

No bugs that I know of. I'm using it on a few live sites. Should be fine.

I forgot this one... http://processwire.com/blog/posts/processwire-3.0.50-core-updates/

I am really missing this module in version 3, are we any closer to an update? I am having to make do with Croppable Image 3, but the crop settings require both width and height values, not allowing either to be flexible.

i have a theme engine module that i use which is part of a suite of modules that together, provide a frontend, or 'markup' api. The Theme Engine handles things like the body classes and is basically a wrapper module for a collection of functions/methods helpful for optimizing front end development. It includes helpers for webfonts and facilitates the handling of the site assets, enabling each template to add dependencies (js or css files, or inline scripts/styles), as well as acting as a wrapper for ProCache whereby it allows the developer to enable/disable ProCache minification as needed. For example, superusers may disable minification and the module will output the individual assets with a url paramter appended to prevent caching. It also provides a simple 'hook' system where the developer can add containers to the main template, into which templates can 'inject' markup, similar to Wordpress do_action. The Meta Engine reads settings from a settings module where the admins can enter the primary settings for the site, such as site title, copyright year and holder, publisher, social media links, contact information and more and provides an easy API to access those settings, as well as formatting for convenience. It also allows for individual templates to add and modify items to the header and footer, such as prefetch/prerender, next/prev, schema, open graph tags, custom favicon sets, and any custom markup. other members of the suite are a Blog Engine, and Events/Calendar Engine.

It might be interesting to have a module with general functions for the many common problems that we find here every day. Something similar to what Ryan did with the uikit file. I know that just could be a simple file for include like _func.php, but I like much more the module format because it's more easy to include it directly from the repository, easy locate the last version (updated, enhanced and fixed) As a plus maybe you can configure which features to include before you download it..

i'm still voting for a solid and core solution of image cropping. using either an exact crop, or predefined ratios, or using a focus area and make it possible to get the right image for the right spot on your template/design and allowing different ratios! but i guess we 2 are in a minority... ?