wbmnfktr

Thank you, guys! Thanks for your feedback, thoughts and preview on your upcoming ideas and projects here and in my inbox. I will sort my thoughts and mix them with your input now. I'll keep you posted on this.

Sorry for being late to the party but I had to look around on that site. As already said here... Awesome!

To make a long story short... the last few weeks I asked myself... "What kinds of ProcessWire Profiles are missing or could be interesting for new/existing users?" The answers were... feature rich - with the full glory/monty of ProcessWire's features basic default profiles - Agency, Portfolio, CV, kind-of-niche (Photographers, Musicians, ...) verbose and detailed for starters Premium Theme - kind of... like WordPress has So I wanted to ask you... what could be interesting for you and maybe others out there. I already created Sublime (theme based), pwRecipes (super basic starter) and PWBrecipes (advanced starter based on pwRecipes) but still... I want to create and offer more options for new and existing users of ProcessWire. I teamed up with my colleague and friend from Muskaat to create a nice multi-purpose theme/design to provide a nice entry-point for everyone in regards of ProcessWire but this will take time as it will be highly customized and art-directed. There is a side-project of mine (some of you may know about it) where I want to provide all kinds of ProcessWire Barebones like an Agency-Theme-themed starter profile and such. But... to be honest... right now I'm a bit lost. I don't know what could be interesting or what might be needed. And yes... I don't know where to start. ? Is there anything YOU wanted to have being around as a site profile or theme or anything like this? Every answer, idea and recommendation is highly appreciated.

I almost understand your need (or desire) for this kind of feature. I have had several situations in which I wanted to show clients or others the backend without the ability to change/save anything while still being able to present the full/all capabilities of ProcessWire (and therefore CKEditor textareas, autocomplete in page references, and so on...). I created dummy instances of ProcessWire to show it and imported database backups a few days after to get everything back to normal. While your idea is interesting in some kind... it wouldn't fit my need to show people all kinds of things ProcessWire can do. They wouldn't see the CKEditor in all of its glory - for example. Maybe I got this wrong but... half rendered pages wouldn't work for most of my suspicious clients in regards of ProcessWire. They want to see the "WORD-like textarea" and want play around with it. Nonetheless I can imagine situations in which this would be handy and a great addition but I really don't know how much work this kind of user permission would cause - either in core or as a module... so... sorry for not answering your question. ? Admin read-only permission: could be nice Demo mode for new clients: oh yes... please A mix of both: well... why not

Good to hear it works now. It would be interesting to see and know how and why ProcessWire rejects some files nonetheless.

That's... weird. I'd try this now. take whatever kind of files to test which will be accepted take the video files and change file extension to .txt or .pdf try weird file names and easy file names - long, short, letters, numbers, all in the mix keep an eye on the dev console for errors enable debug mode and maybe some sort of Tracy Do your files have some sort of special names or characters in the names? Are these files corrupt or are they not properly exported? Are these files real movie files or just MP3s (or other) renamed?

Once I missed to add the file extension to my files field. Took me some time to find that issue. Another time something in Firefox messed things up. While it didn't work in Firefox, all other browsers or therefore the uploads from within those worked without problems. Never found out what it exactly was.

FYI: The FormBuilder cookie feature throws an error when using Foundation v6 as output framework. The other options work without any flaws.

So many new features... so little time. ?

Well... maybe next time. ? Good to hear you found it.

It should. My example above will therefore look in /site/templates/_view/FILE.php - this works in about 99% of all cases. Sometimes... I don't know why it doesn't. In those rare cases I have to write render("./_view/..."). and need to add this ./ before the path.

In addition to my previous post some more details about a problem I recently faced with myStyles.js. The browser console showed the following error: Uncaught Error: [CKEDITOR.resourceManager.add] The resource name "mystyles" is already registered. The template had 3 textarea fields but only one of these fields had a custom myStyles.js. After adding the custom myStyles.js to the other two fields everything worked as expected again. Maybe this detail helps in the future.

Can you post the code that is responsible for rendering/creating those images. Maybe there is a glitch in it.

Weird... the favicon.ico thing works like this: The browser looks in certain places for certain files. The favicon.ico is expected here: https://www.domain.tld/favicon.ico and will be displayed if it exists. You can... nonetheless... define an alternative file as described above to change default behaviour or to show another file like a .png Sometimes browsers are kind of lazy and don't look for new files they either haven't found for a while or have already cached. So using another browser or adding a bookmark to your bookmark bar can help to trigger a reload/refresh.

It might not be related to this issue here but you could try these two things... add namespace <?php namespace ProcessWire; ?> on the very first line use require_once instead of require

Into the web/document root of your site. The same level as index.php.

That should work out pretty well... unless I'm missing an important detail here. But... to be very honest... in order to accomplish and maintain such a setup you should be at least an intermediate ProcessWire-user with some kind of experience. These multisite setups – either option 1 or 2 – bring their very own issues with them and you need to be able to handle those and the whole environment (the hosting and server setup) surrounding them. I'd recommend to set up an instance of ProcessWire for each client just to be safe. One mistake and all your clients would be down/see errors/or whatever. You could repackage customizations in modules and distribute those to each client. That's intermediate/advanced stuff as well but way more secure on a larger scale. If you just want to maintain different sites for yourself... play around and have fun.

It's even easier. Just add a favicon.ico (backend) to and a favicon.png (website) to your web root. For the real website you define something like <link rel="shortcut icon" href="/favicon.png" type="image/png"> While the website shows your .png the backend will show your .ico.

Either what @bernhard said or your path is wrong. The last is the main thing I'm struggling quite often with. When I get my paths right it works as expected. Even with things from repeater/repeater matrix items.

Can confirm this behaviour.

Ok... is test nowadays somehow... protected within page names? I know about issues in field names (back in version 2.whatever.x) but not in page names.

That's weird. Especially as most/all pages within Trash will be re-named.

Ok... well... that's kind of easy as well - or it should be at least for you. As you used Bitnami there should be a dedicated Bitname folder somewhere now. C:\Bitnami User>Bitnami Something like that I guess - I'm not sure as I don't use Bitnami. But... within that default Bitnami project (ProcessWire) folder you will find a folder called site and within that a folder called templates. So... it might be C:\Bitnami\Processwire\site\templates

You could edit the output in the template file and use the new $page->if() method. https://processwire.com/api/ref/page/if/ So there might be no real need in setting a real value. Add a note or description to tell and explain editors the field behaviour. You could define that default value somewhere in your config.php or even in a dedicated settings page to keep it editable - at least for superusers.

Does a clone/copy of that page end in a 403 as well? Are there any hooks or if/else statement in your template that check for specific user roles? Can you find more details in the logs?