horst

Very cool project and fun to read. ?

Hi Robin, the only thing I remember was this: But this was fixed sometime after that thread. Today using the SessionHandlerDB is without this issues.

I would install the 1.0.9 module in PW 2.5 and then upgrade PW to latest 3.x after that upgrade the module. Just my 2 cents.

Maybe you try to configure your webbrowser(-profile), that you use for webdeveloping, to completely disable caching?

Hi @saverio.eyra, if I understand you correct, you want to use the existing website layout and content, but converted into PW CMS? If yes, means, there are not such things requested like redesign, I'm interested in this small project. ? You can PM me here in the forums or contact me via email <info (AT) nogajski (DOT) de> Horst

@teppo, This module is ready to use with the current stable and dev versions of PW (3.0.99+). I know that many users (and me too) actively uses it in many sites. It is also simple to use in conjunction with MarkupSourceSet. So, I think I will not add new features to it, but I will maintain the compatibility of it with future PW versions! Some time ago, it becomes compatible with new UIKit-AdminTheme. Here is a screen:

Hi @daniels, many thanks for that great module! As a little helper, I added a checkbox to the modules config page that can test the current settings. If you don't mind, I sent you a pull request.

I ever use absolute urls, because then I can match them from within different located css files. Normally I store all fonts under /site/templates/styles/fonts/.

something like this should work: <?php class Submissions { protected $site = null; // <= add a handle for the site public function __construct($site) { $this->site = $site; // <= assign the site to the class handle } function insert($data) { $this->site->pages->find(....); // <= use the site through the class handle } } <?php require('/home/centralsite/public_html/wire/core/ProcessWire.php'); $site = new \ProcessWire\ProcessWire('/home/centralsite/public_html/site/', 'http://example.com'); include "submissions.class.php"; $submissions = new Submissions($site); // <= here you pass your pw instance ($site) into your class

If I followed correct, you have a well running local site? You plain copied it to the online space? (Without running an installer before?) Maybe you can try to export your local site with the SiteProfileExporter Module, and then do a fresh installation online. But be aware, that all created roles & users & accessrights get not exported with the SiteProfileExporter Module. This you have to implement manually after installation. The advantage is that you don't have to deal with all the different caches and also get notifications during the installation routine if something with the online space is missing.

Here is some code I used which is working fine: https://github.com/horst-n/LocalAudioFiles/blob/master/site-default/templates/local-audio-files_stream.php#L34-L45 https://github.com/horst-n/LocalAudioFiles/blob/master/site-default/templates/local-audio-files_stream.php#L264

If you are searching for programatically save your own programatical defined sort order, you may find useful code snippets here: Interesting for you are the function(calls) of databaseUpdateSortInPages Also reading the few discussion posts may be of interest.

Use the fields import / export functionality and respective the same for templates. Go to admin fields and click export, then select all the fields you need. Go to admin templates and click export, then select the template(s) you need. Edit: Additionally you may use the API: https://processwire.com/api/ref/templates/get-export-data/ https://processwire.com/api/ref/templates/set-import-data/

@Autofahrn, have you tried out one of the WireMail-ThirdPartyModules?

If you really need to *write* html code, and not to copy / paste some pieces, I second the use of the ACE-editor:

You can add suffixes to image variations. If you want to do it with Pia, you need to add, for example, suffix=lowres, or suffix=hires to the selctor string. If you want to add suffix names to image variations without Pia, pass an options array to the width, height or size methods as (optional) last argument. Within the array set the key suffix to your desired name.

In some cases it is much work to do, for the own business (not related to web business, only) and for building websites. But building or adapting websites for clients to become gdpr compliant is nice, as you now can acquire some extra paid work. ? In the near future, we have to build new sites gdpr compliant from start up. In regard of only trust the lawyers, I have mixed feelings. Sure you can find some usefull infos on eRecht24, but they also claim without warranty. ? And the free generators are very basic. I got me a premium account there, and found some more in depth information. But I think it is important to get the hands dirty by walking through a lot of texts and finding out what is important for one self.

I really like them and uses them since the first minute. Mostly in the functions style. That's how my _init.php looks like <?php namespace ProcessWire; $homepage = $pages->get('id=1'); $kontakt = $pages->get("template=cfg")->kontaktdaten; // der Seiteninhalt: region('header+', ''); // fixed header region('nav+', ''); // ist im header region('hero+', ''); // heroimage region('main+', ''); // bodycontent region('footer+', ''); // footer // alle JS codes die innerhalb document.ready am body ende ausgeführt werden sollen, // nachdem jQuery u. main.js schon geladen sind: region('JSdocReady+', ""); // DebugAusgaben am Ende der Seite region('debug+', ''); If you wonder why I initially define the regions with a + (plus sign), it's because sometimes one may end up with a site that do multiple calls of template render functions on one page, what results in multiple includes of _init.php in the chain. This is to avoid an override of previous values. Of course one of the rare use cases, but not impossible.

Also it maybe an improvement from the other side, to serve your users some filter-lists (dropdown selects) of the products, additionally to the fulltext search field? Here you can see an example with architects in an archive, (realized with url-segements), that only serves all matching archive albums. (could be also only products) Whereas the fulltext search serves also matches in the blog or on pages with matches in different bodytext parts. The fulltext uses %= operator, that also allows to match small text snippets like BRT. (And yes, uses the pipe as OR selector!)

looks like spam!

I really like that PC Buster serves different options! Until now, I use in my own scripts the ?{$fileTimestamp}, but have read about a versioning with .htaccess mod_rewrite here: https://stackoverflow.com/questions/118884/how-to-force-browser-to-reload-cached-css-js-files mod_rewrite on EVERY request and even page reloads for (how many files?) is a lot, whereas if it can get handled safely by the client browsers, it seems to be better for me. I'm interested in getting more information about which option may or may not work in which situation.

@gebeer, there was a change in Session-DB-Handler in the past, but don't remember exactly when. Maybe you compare the current 3.x Module against the 2.7.x one?

whats about detecting it and set it to a session var in site/finished.php and afterwards looking for it in site/init.php? PS: it would need extra attention if a language change url was currently clicked.

Yep, that's with the overhead is right, but only on the first view. If you have many fields and reference fields on one page (template), your searches may become time costy in the DB. At that point you want to use concatenated fields (also available as core module!). So it depends on the amount of your involved fields (=DB-tables) which way to go. EDIT: The core module is called Cache, it is a fieldtype:

Maybe a bit dirty but very effective: add a hidden (or none manually editable) textarea field to your main page and on save of the main page or one of the children, collect all text there in. Then you need to search in this field instead of the (main)-body field.