wbmnfktr

So... when you are your client it's more than easy to evaluate the outcome. You can iterate all steps every single time to come to the best result. Maybe you want to outline the expected result on your own and want to discuss this here or you want to contact @ryan as a mastermind of ProcessWire to incorporate everything with him.

I totally agree with that but pages in pages under pages (repeaters) is something different. So plain pages are always more easily to control.

I'd say you or your client should outline the result and therefore you should team up with some advanced people here. Your project sounds really complicated at first but although it seems to be very forward in kind of business logic (what parts of items on each page etc.). Being clueless is totally fine. I don't know at which stage your project is, but it seems you still can control the outcome. I think there is no tutorial to show you the right way for your project right now but with more details about the outcome there might be more users that can help you with that. As always: clients WANT everything without knowing ANYTHING. So you have to define the way.

Can you define what's need to be accomplished?

?

Never ever give endusers too much options as in decisions. A lesson I learned way too early. Give them pre-defined options (for example: 2-columns, 3-columns, 4-columns, big jumbotron, small jumbrotron). Pre-defined sets of settings work much better than fully customizable parts - for my clients and for my cases.

Honestly... go with pages for each event. It's much easier to handle and much easier to [everything]. Repeaters are nice but events/dates/calendar entries are more than just an item in a page. If you used pages instead of repeaters you could use: <?php $eventsToday = $pages->find("template=event, date=today"); ?> Just create a root element, for example: page with template events, for all your events and place all evens underneath it.

I don't know if this will help you but in the last 2 years I/we created several sites and therefore used ProcessWire to manage all of their content. First of all we created plain HTML/CSS prototypes with almost every detail needed. Afterwards I/we created the logic in ProcessWire. Inspired by other page/article builders we created things in ProcessWire with Page Tables (extended) and the the ProField Repeater Matrix. Based on your knowledge in ProcessWire syntax, logic and modules your outcome may differ from simple site structures to absolute individual page/site constructs. You might want to look into the showcase section to find out what others build already. As a starter in ProcessWire you might also want to team up with one of the more advanced users to help you building sites.

Same here. ProCache ProFields FormBuilder Just perfect. Hope I ever told @ryan this. ?

If someone is interested in completing this list of Pro ProcessWire Arguments: https://github.com/webmanufaktur/pw-arguments Already added those from @dragan. Just collecting all arguments we can find. We can later on sort them by groups (for example: marketing, devs, users, clients, ...)

Glad it works this way. You might consider using PW ProCache. It does all this minifying and compiling stuff PLUS awesome and reliable caching. It's paid I know but it's worth every cent.

The problem is that the definitions of real data, studies and 3rd parties have a super broad range. I personally understand them like this: real data = comparable numbers or features studies = examples, references, sites built with ProcessWire 3rd parties = ProcessWire experts (long time ProcessWire users, integrators and developers) We are all 3rd parties (experts) that could create any kind of studies (show examples and projects) to show real data (used features, development time). The videos Jonathan created are a super nice look behind the scenes for someone who is already in web development and CMS-things. My clients aren't into this. They ask me to give advice. They trust me. They want me to tell them what they need. I am the 3rd party (expert) that knows about pitfalls. Let's turn things around. We shouldn't compare ProcessWire to another CMS. We should show and tell the benefits of ProcessWire. For example: ProcessWire is easy to extend. ProcessWire is easy to use. ProcessWire manages all kinds of data structures (books, movies, cars, clothing, what, ever, ...) right from the start. ProcessWire generates all kinds of data exchange formats (RSS, XML, JSON, CSV, ...). ProcessWire doesn't need a dedicated or specialized hosting to perform well. ProcessWire is highly customizable. ProcessWire delivers what is needed. [Your statement here] Just my two cents.

There could also be an issue with AIOM and PHP 7.x There are more threads with this issue - see below: I'd bet you find a solution in them for your problem.

Should be easy to fix.

It seems some resources were loaded non-secure over http:// Try this: https://www.whynopadlock.com/

Checked some sites and no extra space. Even imported some new entries into text fields. Import Pages from CSV 1.0.6 ProcessWire 3.0.99

Oh... kay... as I use the CSV import module a lot I should check my sites to verify this issue. I never noticed any extra space so far but I will have a closer look now.

Did you look into the database itself to verify that there aren't any gremlins in those street names? What happens when you look for pages containing the streets that cause an sort issue? Do you find all entries or only a few? There is one thing... ok, that shouldn't be the problem but... does ProcessWire stumble over street and street_number?

I don't know if this helps or if you already tried it but... .. does $pages->find("template=user, roles=member, limit=100, sort=street") work on its own? .. does your example work when there is no limit in it? .. does it work without pagination? .. are those wrong sorted entries in any kind special or do they have something in common? .. does it work in your dev-environment?

I'm out of ideas right now. When your db host is fine and (as I assume) your db credentials are correct too there isn't much left to check. Have you tried to connect to your db with a simple PHP script to verify the database is working?

Please double check your database server host. As far as I know DomainFactory offered different versions of MySQL and your error message indicates a not supported MySQL version. For example: mysql4.domain.tld = MySQL 4.x mysql5.domain.tld = MySQL 5.x (should be used as we want MySQL 5.x)

My fault. Even in Dev Tools / Inspector there is nothing. Ok... you found it already.

ProcessWire 3.0.106 and no inline styles so far.

Problem already solved in another thread.

You want to trigger GIMP/Photoshop server-side? That might get out of control. ?