Leaderboard

Hello, I just want to point out this framework for making html apps https://onsen.io/ it's compatible with jquery, angular, vue, react or any other js framework. So far I made an app using this and bootstrap with https://propeller.in/ for the desing and some libs like jquery and lodash for the app logic I prefer this to other alternatives like ionic since it does not bound you to angular or react. Cheers

Looks like CKEditor 5 is on the way: https://ckeditor.com/blog/CKEditor-5-A-new-era-for-rich-text-editing/ https://news.ycombinator.com/item?id=15497972 (HackerNews comments of the above article) Home page: https://ckeditor.com/ Demo: https://ckeditor5.github.io/ Feature Video:

Done too! Its updated to 0.2.7. All in all we only used 7 minutes to react on Charles issue report! Cool!

I've run into this issue a few times...extremely frustrating, until you figure it out, of course After some snooping I determined it has to do with mod_pagespeed's elide_attributes flag, which removes default values, i.e. <select multiple="multiple"> becomes just <select multiple>. Unfortunately, Inputfield asmSelect's JS hooks onto select[multiple="multiple"], and thus skips those elements when the value isn't explicitly set. Long story short, remove elide_attributes from ModPagespeedEnableFilters in pagespeed.conf, restart your web server, and it should work.

Update: Multi Sites Version 0.0.2. Multi Sites can now install single/stand-alone sites! The Multi Sites in the name now means installing and managing multiple sites ! For single sites use, the module now downloads, strips, compresses and save ProcessWire versions of your choice for reuse (rather than downloading each time you install a single site). These ProcessWire files can be refreshed on demand, e.g. when a new version of ProcessWire comes out. README is now complete. See changelog for more details. Download from GitHub. Changelog Support for installing single/stand-alone sites. Added Type or Paste and Install Configuration methods for creating sites. Create and edit site install configurations. Download, store and restore various versions of ProcessWire (for single-site installations). UI enhancements. I'll update first post later. Screens 1 2 3 4

To enable markdown, you have to install the following core module : ... then you have to apply the Textformatter to your field. Go to the Details tab of your field, select the Textformatter(s) you need then save. Did you mean you clicked/installed the Front-end page editor ? If yes, simply uninstall the module PageFrontEdit. You might need to remove some markup depending on the option you choosen. And welcome

Hey Sam, Welcome! It's definitely possible to build something like that. There's a few reasons why you didn't find an exact module for what you're trying to do. ProcessWire is more of a development framework and toolset than a plug-and-play CMS. It provides you easy access to a relational database, user and session management, querying, and front-end rendering through its API. As that's the case, much of what you want to do – create product records with categories and tagging, and query those records with those fields – can be done pretty easily with native PW functionality. A skeletal walk-through of how you might do this: Create a Product template in the admin. Create the fields you'd like for the Product – probably a Title, Body, Categories, and Tags. The last two could either be hard-coded (as a Select – more rigid) or relational (as a Page Reference/PageArray, using other Pages as data – more flexible). Create Pages with the Product template, and populate the data. Create a Product front-end template, /site/templates/Product.php (file shares the same name as your admin template name), with code like this: <h1><?=$page->title?></h1> <div class="body"> <?=$p->body?> </div> <div class="categories"> <?php foreach ($page->categories as $c): ?> <?=$c->value?> <!-- This is assuming your Categories are a simple Option fieldtype, without titles. --> <?php endforeach ?> </div> <div class="tags"> <?php foreach ($page->tags as $c): ?> <?=$c->title?> <!-- This is assuming your Tags are a Page Reference fieldtype. --> <?php endforeach ?> </div> Edit your front-end home template, /site/templates/home.php, and list some of your Products, maybe like this: <ul> <!-- List pages with Product template, limit results to 10 --> <?php foreach ($pages->find('template=Product, limit=10') as $p): ?> <li> <a href="<?=$p->url?>"> <?=$p->title?> </a> </li> <?php endforeach ?> </ul> That'll get you started with displaying and querying Pages. You might want to take a look at this article to better understand how Templates, Fields, and Pages relate to each other. E-commerce is one of the less well-represented areas of ProcessWire, but is 100% doable. The main bits that don't exist out-of-box are a shopping cart, order management, and the checkout process, but could definitely be built using PW. The module Padloper has both a cart and checkout process. You could get something mostly self-contained like Stripe or Snipcart running within a PW install in short order. Whatever the case, E-commerce in PW, and in fact most systems, will require some development and figuring out. Hope that helps!

So now there are 2 modes that the process pages can be rendered in, Field Render Mode and Template Render Mode; in field render mode, you just select the field to render and that's it; if you use the built in CSS, shortcodes and such you can output those simple tabbed help pages or just plain wikis. if you need more options you can disable the default css and use your own css file, or multiple css files; a.k.a Field Render Mode, advanced settings. Here is a simple wiki page, using a custom CSS file (to make it a bit more wiki-looking): In Template Render Mode, you activate that by just putting the name of the directory where you will store the template files, within your templates directory. This mode is not mutually exclusive of Field Render Mode; they both work depending on the factors; Once you are in Template Render Mode, you have to load all of your own dependencies; in other words, the module just lets that file take over, and renders it; The only thing the module does in this mode is sets output formatting to true on the page being rendered, before sending into the wireRenderFile method. Here is an example of a page being rendered in Template Render Mode; for this to work it requires a matching php file to the name of the page, so this is being rendered by news-help.php inside the folder: Here is the code in the news-help.php file. $jqt = $modules->get("TextformatterJqueryUITabs"); $mcs = $modules->get("TextformatterMarkupCSS"); $body = $page->body; $mcs->format($body); $jqt->format($body); $config->styles->add("/processwire_test1/site/modules/ProcessDocumentation/ProcessDocumentationDefault.css"); echo '<div class="help-doc">'; echo $body; echo '</div>'; The only exception to the use of both modes is if you create a default.php file in the folder; if you do that, then the module will always render the pages using that file; So this way you can have all of your document pages being output by that one file and not have to create new php files for every new doc page; Since you can do anything you want in those php files, you could show some content from another site. Here is an example where the php file loads a github readme file: $markdown = file_get_contents("https://raw.githubusercontent.com/outflux3/InputfieldSelectize/master/README.md"); $tfmd = $modules->get("TextformatterMarkdownExtra"); $tfmd->format($markdown); $config->styles->add("/processwire_test1/site/templates/docu-templates/test-wiki.css"); echo '<div class="help-doc">'; echo $markdown; echo '</div>'; ... and the page:

This module is on Github, https://github.com/outflux3/ProcessDocumentation in case any one wants to test it; will wait till i have time to run test cases before releasing..

I always look for free HTML templates or buy one for about $10. It takes me to about a day to incorporate it in PW. After that you have all fexibility of PW with a kick-ass template.

Super handy, thanks! I issued a pull request for more efficient query syntax, i.e. using prev() & next(). I have an install with 1700+ siblings and the admin clearly was getting bogged down. These changes fixed it.

Hi @abmcr Try: foreach($page->images->shuffle() as $image) { echo "<img src='$image->url'>"; }

Done.

This is one of my scripts that I use to quickly regenerate caches when I flush them. It wont work for dynamically generated urls (i.e. urlSegments), obviously <?php use ProcessWire\ProcessWire; require_once 'vendor/autoload.php'; $wire = new Processwire(); // get urls for all public accessable pages $urls = []; foreach($wire->pages('id>0, check_access=1') as $p) $urls[] = $p->httpUrl; header("Content-Type: text/plain"); // visit all urls foreach($urls as $url) { $ch = curl_init($url); curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_exec($ch); if(! curl_errno($ch)) { $info = curl_getinfo($ch); curl_close($ch); echo 'URL: ' . $url . "\n" . 'Status: ' . $info['http_code'] . "\n"; sleep(0.5); } else { echo 'ERROR: ' . $url . "\n"; } } Save this in the same directory as index.php, such as cache.php then access it from mydomain.com/cache.php. It might take a while before anything to appear until output buffer is flushed to the browser.

I found this to be a great approach for using Grid today: https://www.smashingmagazine.com/2017/06/building-production-ready-css-grid-layout/ One caveat is that you naturally can't use "grid in grid" for navigation layout etc..

intercooler.js (which I may have mentioned before ) has beta support for Server Sent Events. I haven't tried SSE, but I'm a big fan of intercooler generally.

Send AJAX requests to poll the server for updates. Easy to implement but puts strain on the server. Use long polling (reply to a request only when there's an update on the server). A bit more difficult, but fewer unnecessary requests. Use websockets (Socket.io, Pushy for push notifications) or SSR (server sent events). Ideal, but a bit more involved to implement.

Aah, thank you @szabesz, I'm not going mad after all, just a little senile, perhaps. Sorry to all for the confusion.

https://modules.processwire.com/modules/textformatter-pagination/

This one? https://processwire.com/talk/topic/17477-dummy-text-generators/?do=findComment&comment=153638

This is odd - I thought I'd replied to this thread on Monday but there's no sign of that post. (Has there been a problem?) Anyhow, I accepted & merged @netcarver's pull request, thanks for that. And I think going forward that making the module configurable so that a selection of text files can be chosen from might add to its usefulness.

There exist two Pro modules which will help you to build this e-commerce website. Padloper (already mentioned) and Variations : https://variations.kongondo.com (check the tutorial and the video) Also there are two good reads on Snipcart, a tutorial and a case-study - a must read even if you plan to not use Snipcart: https://snipcart.com/blog/processwire-ecommerce-tutorial https://snipcart.com/blog/case-study-ateliers-fromagers-processwire Welcome to the forum @Samk80 and good day to you

Thank you @SamC It does have some problems, I am aware. It's an elephant to load and very experimental, so it's a bit rough. In fact, the engine (whitestormjs) was being developed as this site was implemented, with this site serving as a guinea-pig to discover issues, find missing features and whatnot. That by itself is a bit dangerous. The web is so volatile that instead of polishing too much, I'll probably wait until I have a couple more case-studies to add and cook up a new site with some fresh experimental stuff and a whole new set of problems

Sites Manager 16 September 2018: FOR NOW, PLEASE DO NOT USE THIS MODULE IN A PRODUCTION SITE. A RECENT ProcessWire UPDATE HAS BROKEN THE MODULE. I AM WORKING ON A FIX. ################ Sites Manager is a module for ProcessWire that allows Superusers to easily create/install ProcessWire sites on the same serverspace the module is running in. Only Superusers can use the module. You can create both stand-alone and multi-sites. Single/Stand-alone Sites Stand-alone or single-sites are sites that will run in their own document root/directory with their own wire and site folders, .htaccess, index.php, etc. In other words, a normal ProcessWire site. Multiple Sites Multi-sites are sites that will run off one wire folder (shared amongst two or more sites) each having their own site folder and database. In this regard, it is important to note that Sites Manager is not in itself a multiple sites solution! Rather, it is a utility that helps you create multi-sites to be run using the ProcessWire core multiple sites feature. For more on this core feature, see the official ProcessWire documentation, specifically the solution referred to as Option #1. Option #1 approach requires the site admin to initially install ProcessWire in a temporary directory for each new site. The directory then needs to be renamed as site-xxx, where ‘xxx’ is any name you want to use to differentiate the installation from other sites, before it is moved to the webroot. For instance, site-mysite, site-another, site-whatever. In addition, the /wire/index.config.php file must be copied/moved to the webroot. Each time a site is added, the index.config.php has to be edited to add ‘domain’ => ‘site-directory’ key=>value pairs for the site. This process can become a bit tedious. This module aims to automate the whole multi-site site creation process. The module is based off the official ProcessWire installer. Creating a site is as simple as completing and submitting a single form! You also have the option to type and paste values or reuse a pre-defined install configuration. The module will: Install a ProcessWire site in your named directory, applying chmod values as specified Move the directory to your webroot Update/Create a Superuser account as per the submitted form, including setting the desired admin theme and colour For multi sites, update sites.json (used by index.config.php to get array of installed sites) For multi sites, the only difference in relation to the core multi-sites index.config.php is that this file is slightly different from the one that ships with ProcessWire. Download from GitHub: Sites Manager (Beta Release) Features Install unlimited number of sites in one (multi-sites) or independent (single-site) ProcessWire installs. Install by completing a Form, Typing or pasting in configurations or using pre-created install configurations. Choose an Admin Theme to auto-install along with the site installation. For single-sites installation, download, save and reuse ProcessWire versions of your choice. Install and maintain site profiles for reuse to create other sites. Create install configurations to speed up installation tasks. Client and server-side validation of site creation values. Edit uploaded profiles (e.g., replace profile file). Lock installed sites, configurations and profiles to prevent editing. Bulk delete items such as site profiles, installed site directories and/or databases (confirmation required for latter two). View important site details (admin login, chmod, etc). Links to installed sites home and admin pages. Timezones auto-complete/-suggest. Pre-requisites, Installation & Usage Please see the documentation. Technicalities/Issues Only Superusers can use the module. ProcessWire 2.7 - 3.x compatible Currently using ProcessWire 2.7 installer (install.php) For multi-sites, potential race condition when sites.json is being updated on a new site install vs. index.config.php accessing the json file? Not tested with sub-directory installs (for instance localhost/pw/my-site-here/) Currently not doing the extra/experimental database stuff (database charset and engine) Future Possibilities Install specified modules along with the ProcessWire install Profile previews? Credits @ryan: for the ProcessWire installer @abdus: for the index.config.php reading from JSON idea @swampmusic: for the challenge Video Demo Demo showing how quick module works on a remote server [YMMV!]. Video shows downloading and processing two versions of ProcessWire (~takes 7 seconds) and installing a single/stand-alone ProcessWire 3 site using the new Admin Theme UI Kit (~2 seconds) on a remote server. Screens 1 2

Hello, I am testing Processwire. Usually, we can found many templates but, here, I an't found. Only existing sites. Nobody share template for free or not ? Thank you

No don't do that. 'windowTitle' and 'headingSubtitle' are fields I created on MY own site. You more than likely don't have these fields. Whats happening is this (as per your example earlier): <title> <?php // any page OTHER THAN the home page if($page->id > 1) { // prints 'Employer branding - pracownik staje się klientem -' echo $page->title .' - '; } // prints 'Agencja PR Q&A Communications – Poznań, Gdańsk, Warszawa, Bristol' echo $home->title ?> </title> So that bit of code outputs: Employer branding - pracownik staje się klientem - Agencja PR Q&A Communications – Poznań, Gdańsk, Warszawa, Bristol ...which is what you are seeing and you referred to it as: If you just want the first bit, then you just need: <title><?php echo $page->title; ?></title> I'm not even sure if you can log into the admin on your site? If you can, you will see the 'Title' field on each page if you edit it. Browsing your site, look at the page titles and you'll see what's happening: http://www.qacommunications.com/ (Agencja PR Q&A Communications – Poznań, Gdańsk, Warszawa, Bristol) http://www.qacommunications.com/pl/kariera/ (Dołącz do nas! - Agencja PR Q&A Communications – Poznań, Gdańsk, Warszawa, Bristol) http://www.qacommunications.com/pl/zakres-dzialan/ (Zakres działań - Agencja PR Q&A Communications – Poznań, Gdańsk, Warszawa, Bristol) http://www.qacommunications.com/pl/biuro-prasowe/ (Klienci - Agencja PR Q&A Communications – Poznań, Gdańsk, Warszawa, Bristol) See what the code is doing now? 'Agencja PR Q&A Communications – Poznań, Gdańsk, Warszawa, Bristol' is the 'Title' field of your homepage. This is being appended to every other page title on every page other than the homepage.

@abdus please update the version too in your PR. Thanks.

The get method generates the cache if no cache is found, if you pass it a function/closure. And with a hook (on page save or wherever it makes sense for your use case) you can generate/update the cache.

Hey desbest, what version of processwire are you currently using? If you are using 3.x.x, you will probably need to incorporate <?php namespace ProcessWire; ?> into your template files. However, there might be a few other things needed as this profile was introduced 5 years ago and has been removed from the Site Profiles currently in the modules directory. There is though an updated version by @dadish that updates it to v3.x.x, and it can be found here.

Checking for empty value is usually enough $emptyPages = $pages->find("myField=''") // note the empty string with single quotes $filledPages = $pages->find("myField!=''")

I have searched for a solution. I would shorten the text from my blog entries. This seems to work for me. It keeps the html tags from the editor: function truncateHtml($text, $length = 100) { $current_size = strlen($text); $diff = strlen($text); $remainder = $current_size - $length; while($diff > 0 AND $remainder > 0) { $pattern = "/(.*)[^<>](?=<)/s"; $text = preg_replace($pattern, "$1", $text); $diff = $current_size - strlen($text); $current_size = strlen($text); $remainder = $current_size - $length; } // iff $diff == 0 there are no more characters to remove // iff $remainder == 0 there should removed no more characters return $text; } It's from here: https://stackoverflow.com/questions/38548358/cut-html-input-while-preserving-tags-with-php Post Number 4.

There is also the site export profile module. Works very nice. http://modules.processwire.com/modules/process-export-profile/

i think i would create a single blog-entry template with a repeater holding one ckeditor body-field. 1 repeater entry = single page blogpost more repeater entries = blogpost with multiple pages based on url-segments you could show the corresponding repeater item. without url-segment it would show the first. all other content would always be the same (like a comment section, for example would show up on all pages, like here: http://processwire.com/docs/tutorials/hello-worlds/ )

I don't think we can use grid for global layout soon. But for single components it can be just as useful in places and it doesn't seem like to much of a hassle to have less sophisticated looking fallbacks for those smaller usecases.

this looks great, thanks for sharing! i hope we can get the drag image support into processwire too. that's one of the few things that always needs some explanation for my clients...

Not, it's not late at all. In fact, I forgot to mention it. I was looking for name suggestions! (one of the reasons I still left it in Alpha, actually). Thanks! I like sites manager. Let's see if there are more suggestions. All, Module Name Name suggestions for this module please? We currently have: Sites Manager Upgrading Please note, version 002 includes some templates not in version 001. A re-installation is required I am afraid.

Yes. Try exporting in portions. Or better yet, export your database, import to production, copy over files, modify config.php and you're done.

Great news! Now I just have to find the time to try it out... BTW, how about renaming it to something like Sites Manager? Is it too late to rename it to something more descriptive and less confusing? There is another group of modules with almost the same name: https://modules.processwire.com/modules/multisite/ https://github.com/somatonic/Multisite/tree/dev2#add-multisitedomains also: https://processwire.com/api/modules/multi-site-support/ Multiple solutions with multiple multies in their names are a bit confusing

There is one big advantage of "non-standard" names like "Settings Train" – or ProcessWire for that matter – and it is that it's easy to search for them. "SettingsTrain" is already number one result in Google.

As much as I love trying out new CSS, I only ever use safe (ish) techniques so grid will have to wait for me. Probably at least another year as I've only just ditched floats for flexbox.

Have you tried using one of these? https://processwire.com/blog/posts/find-and-iterate-many-pages-at-once/ https://modules.processwire.com/modules/pages-sum/

From the documentation you linked to: https://processwire.com/api/selectors/#sort

Welcome to the forums and to processwire @Eljeff! Currently, processwire does not have ready made templates to drop in, or a marketplace for such things. However, when you install a fresh copy of processwire, you get several site profiles to use, and there is a bootstrap profile out there. One of my favorite things of processwire, is that is is very simple to get a basic site up and running. With just a few if/foreach loops and echo's, you can get a simple site going very quickly. This makes it super easy to integrate your own framework/css into the mix. @flydev has shared these videos which will help out in the start of your templating:

hi macrura! nice to see the progress. i hope nobody gets me wrong but i still think that going with native pw modules (fields) could have some real benefits. i try to explain what i mean and how i came to that opinion... my first impression when i saw your screenshot was, "very nice". i then asked myself how easy that could be built with a process module and InputfieldMarkup... The dashboard example would be quite easy, consisting of only 3 fields with some markup. but still it would need some coding, of course - and that might be a little more work and a little more time needed than your quick ckeditor solution. but still i'm confessed that working with native pw fields is much cleaner than hacking around with hanna codes and several nested tags inside a ckeditor field. that feels like i get thrown back to my old joomla days where we had only this one huge content field and had to do all the magic with messing around with tags and replacements and so on i hope you get what i'm trying to say. btw: i was thinking if i'm messing up your thread with my post, but as it is a preview thread i think discussion should be welcome now my idea that could combine both worlds: first i thought, "why not using some InputfieldMarkup for the content instead of the whole Process?". you are creating a process page that renders one field of a selected documentation page. i thought, what if we had some fields on that page where we can select the content that gets rendered. then i thought we already have this kind of fields: InputfieldRuntimemarkup. So we would need a quick and easy way to arrange those fields! We already have it: The template editor. I'm using ProcessPageEdit all around my CRM application and it works well for presenting data. It has a clean interface and all you need for arranging your content (fieldsets, tabs, toggles etc - i already mentioned that in my post above). So what if we showed the ProcessPageEdit of the documentations page directly to the user? Admins could modify content quickly and easily and for users we could set the visibility to "locked". this would result in something like that: ckeditor fields would get rendered as HTML, image fields would get rendered as gallery and we could do whatever we want with RuntimeMarkup fields. We would have all the built-in pw magic, we would have a consistant styling (for all admin themes, not only for the one your stylesheets are optimized) and many other benefits. what do you think?

Yes, add fields for all the settings you need (e.g. with @Soma's ColorPicker module). Then add the styles inside style.php like you quoted above. body { background:<?=$page->bgcolor-field ?> url(<?=$page->bgimage-field ?>) no-repeat; } /* ...any other styles, with or without PHP code */ Then, in your regular template file, include the CSS settings page. <link rel="stylesheet" href="<?= $pages->get('/your/css/page/')->url ?>"> Basically, you've now created a separate PHP file for all the CSS so you don't have parts in a regular stylesheet and others in your template file. Once everything works, you can go into the style template's settings and switch on caching. Enter a cache time (like 86400 to regenerate the CSS only once a day) and you have performance close to a flat file stylesheet.

There's nothing to integrate, array-config is a joke repository :), it's just there to show that you can you can return variables from files and use them with include statement, instead of dealing with parsing, validation of JSON/YAML etc. I want the same thing with @adrian, which is essentially how getModuleConfigArray() method of ConfigurableModule interface works. public function getModuleConfigArray() { return [ 'colors' => [ 'type' => 'radios', 'label' => $this->_('Color Set'), 'options' => [ 'classic' => $this->_('Classic'), 'warm' => $this->_('Warm'), 'modern' => $this->_('Modern'), 'futura' => $this->_('Futura') ], 'value' => 'classic', 'optionColumns' => 1 ] ]; } Exactly. Also, I agree with @tpr and @szabesz on the naming. While fa-train looks really smooth, fa-industry or fa-wrench isn't too bad either. We really should switch to Material Icons, though. There's an icon for everything, and every icon is crafted with top notch attention to detail. FA looks quite rough in comparison. Small list of Font Awesome icons can be replaced with their Material counterparts, or both can be combined

Done. https://github.com/horst-n/WireMailSmtp/pull/9/ Here's how it looks now:

@horst, I'm not sure how you'd feed about this but do you mind if I fix labels, icons a bit and send PR for it? I mean turning this: Into something like this:

It's hard to keep track of these great modules! That's exactly why I made it. Thanks. Just committed changes to enable pretty much exactly what you asked. Tags now work like this - [dc3] - Show 3 paragraphs ([dc:3], [dc3p] & [dc:3p] all do the same). (Same as original functionality.) [dc3-6] - Show 3 to 6 paragraphs randomly per page load ([dc:3-6], [dc3-6p] & [dc:3-6p] all do the same). (New stuff.) [dc3w] - Show 3 words ([dc:3w] does the same). (Same as original functionality.) [dc3-6w] - Show 3 to 6 words randomly per page load ([dc:3-6w] does the same). (New stuff.) (Anyone who has already downloaded and is happy has no need to update - the only changes are in response to @abdus's request above.)

I think that can be done, although it's going to be stretching my limited regex skillz. Going to be some time next week at the earliest, though.