ottogal

Kudos for the launch of the new website! I share the reservations about the animations, and I find nasty the huge file size for the h1 headlines on non-mobile devices. And the styling of the buttons is ugly. Of course, it's all a matter of taste, too. But I found a bug: At the bottom of nearly every page there are links to the top level pages, e.g. to Blog. But the href attribute of this link is "blog/", that is, relative to the actual page. So the link results in the 404 error page when the link is on a subpage, say on processwire.com/about/ - there is no page processwire.com/about/blog/!

Hi Roych, a nice module, well done! Just one suggestion: In your display the seats are looking downwards (the stage is at the bottom). Wouldn't it be more intuitive to make it all upside down? (That's usually the case in seating displays of airline services during the reservation process.) The advantage is a more natural orientation when booking : The seat to the left of yours also appears to the left in the display. Best wishes ottogal

To separate the status options for one group to the ones for others, why not have a separate Status Page (and status template) for each group: |-- Course Status (template = course_status) | |-- Status A (template = status) | |-- Status B (template = status) | |-- Status [...] (template = status) |-- Master Status (template = master_status) | |-- Status A (template = status) | |-- Status B (template = status) | |-- Status [...] (template = status) |-- Workshop Status (template = workshop_status) | |-- Status A (template = status) | |-- Status B (template = status) | |-- Status [...] (template = status) In the course template you would have PageReferenceFields to each of them, and you would hide the ones not matching to the Parent page of the actual course. There's no conflict having the same status name in different groups. You could even adress different details (e.g. a status "open" could mean other details for a Master course than for a Workshop course).

Guten Tag herr rilke, This might be helpful: https://processwire.com/blog/posts/building-custom-admin-pages-with-process-modules/

As a non professional webdesigner (pure amateur...) I'd like to add to the discussion of versioning. I experienced that a potential "client" I wanted to convince of PW got the impression that in 3.0.xxx the quickly increasing values of xxx would indicate a continously need of fixing lots of bugs. (At the end he changed his opinion.) But also for me it's not comprehensible that we didn't have steps to 3.1 or even 3.2 back already, since there have been some notable achievements in the meantime.

I used the Update option in Tracy's Module Information from the Admin (and used the Delete button in the module's Settings afterwards). In site/config.php I had the permissions set to $config->chmodDir = '0755'; and $config->chmodFile = '0644'; Maybe this '0644' prevented the update of the file adminer-4.8.1-mysql.php and others. In fact the actual version was 7.2, I didn't recall having upgraded one day. (It's indeed a years old site not touched often later.) But sure, I should update anew. Many thanks for your considerations, @adrian! ottogal

FYI: Just updating the TracyDebugger module did not affect the files and directories in the panel/ subdirectory. I had to delete Tracy and reinstall it to get that solved. (Perhaps because of the PHP version being very old, too: 5.6 )

Thank you for the quick reply! I'm planning to get more into the details of the great Tracy module...

Hello to this tremendous community! The hoster of one of my ProcessWire websites is warning me about a critical vulnerability caused by the Adminer module: So I've got some questions: (1) My installed version of TracyDebugger is v 4.19.33. (I didn't use it much, so never considered an update.) Would it be sufficient to update it to v 4.25.22 to fix the problem? Or would I need a seperate update of the Adminer module? (2) I also thought of just uninstalling the module ProcessTracyAdminer. When trying this in the Admin, I'm told to manually delete the respective files and directories. Presumably I'd want to delete the file ProcessTracyAdminer.module.php and, in the panel\ subdirectory, the file AdminerPanel.php and the subdirectory Adminer\. Am I right - or is there more to it? Any insight is much appreciated! ottogal

I never used repeaters, so can't help here...

Hi joe_g, I'd recommend to read this fine tutorial written by kongondo a few years ago: Tutorial: Approaches to categorising site content That's the right "PW way" doing it, profiting from the great API. Good luck! ottogal

In your CSS you have .uk-container { display: flow-root; box-sizing: content-box; max-width: 1200px; /* <<<< */ } That's the culprit.

I'd try findOne() instead of find().

A really great write-up! Should find its way into the Showcase...!

On that page it says Suche nach "festival für freunde" It might be a case issue. Usually a search term in double quotes is case sensitive.