kongondo

Maybe @adrian knows. Let's get his thoughts.

Just to add on to @MoritzLost example, you might want to consider two things: Limit the search results ? Ignore some words, maybe based on their length (e.g. in case you decide to use % operator, ignore two-letter words) or 'common words' (e.g. ignore 'and', 'there', etc..).

Hmm.. Too many tabs already? ?

I agree, but even the small sip should taste like the beer. If it tastes like anything else other than the beer, then one may not be interested in the drink. The gist is if even the simple examples don't work right out of the box or are confusing (small sip of beer tastes like....[insert non-beer drink here]), then one may go elsewhere for their beer... [insert other non-ProcessWire CMS/CMF here]). Besides, it just screams unprofessional/rough edges, etc. What @adrian said ?.

@Tom. moderator note I merged your thread with this one since it's already discussing the topic and issues you raised. I can't find them now, but @adrian has also raised similar points about the functions API in this or an earlier thread.

As always, excellent write-up! Clear and concise ?. If I had the money and you had the time and interest, I'd pay you to write many more ProcessWire tutorials ?.

Shop Dashboard/Backend GUI Hello good people. It's GUI Time! It's time to start thinking about the backend GUI (your Padloper shop Admin/Dashboard). I'd like to hear your thoughts regarding the layout. What is your general preference? What would your clients prefer? The options are: 1-column layout with horizontal dropdown menu (orders, products, reports, etc) 2-column layout with vertical sidebar menu on the left and main content on the right (maybe with an option to collapse the sidebar) Shop resembling an app (meaning will look different from rest of ProcessWire admin). Another variation could be a full-width screen. This would also look different from the rest of the ProcessWire admin. I am leaning toward #2. Alternatively, we could make this configurable and offer two choices; either #1 or #2. Thoughts? Thanks.

Great! Glad you got it sorted. If it works, I'd enable HTTPS for frontend ?.

I think this is the issue (HTTPS would pass through Apache port 443 as opposed to normal port 80). Could you try and disable HTTPS for admin login and see if it works? Since you cannot login, you can either do this on a fresh install or you will have to edit the home template entry in the database. Do you have access to the database? Is the frontend serving HTTPS content OK?

What is the exact error message? What do Apache error logs say? What is chrome/firefox showing in network tab? 403? Maybe temporarily set debug on in /site/config.php to see if you can get a better error message (I doubt though, since it seems this is stemming from a server mis-configuration and ProcessWire does not even come into play)

Maybe Ryan can introduce pagination in the public API ? E.g.: ../exportjson?limit=10&start=350 This is not uncommon in high-traffic public APIs.

My question was about the pictures you were talking about. Are those inline pictures as opposed to pictures (images) saved in an Image field. It is sort of a tangential question :-).

You must have edited the wrong file then ?. That's exactly where it is.

Are you talking about inline-images?

You got a small typo:

Hey @genericFJS. Welcome to the forums. Yes. I think it is a bad idea. It seems to me that you are including PHP in your content? Any reason why you need to do this? If you wanted some logic within the text, you can use Textformatters instead (like Hanna code).

Aren't we already ???

It says it right there in the error ?, Your function shopifyInit() expects a single argument/parameter but here: you are not passing it the $event. edit: I'm too slow; what @flydev said ?.

So you are not running ProcessWire directly then? Any reason you are bootstrapping? I'm not saying this is the cause for the slowness, just wondering. Not sure if this is still the case, but there have been reports of docker being slow on Macs, generally (as well as when tty = true. => not sure about this though). Other than that, nothing out of the ordinary jumps at me RE your Dockerfile. Let's get a few more thoughts.

Welcome to the community @SqANT, What's your server setup? Is it slow in the backend or in the frontend as well? I run ProcessWire in a docker machine and it runs just fine. I'm on a linux box. I use both PHP 7.x and 5.6 without issues.

I prefer this... +1

Yes, it works fine for me, thanks.

This sounds like a Twig issue. I've never used Twig so can't help, unfortunately.

This is great! I know it is a lot of work but it would be really nice to have inline comments about what areas/elements the different styles target. An accompanying cheatsheet or graphic could also do the trick.

Robin, the CSS is not loading for me (you preview). Dev console throws an error as well about $ not defined.