wbmnfktr

Ok... that looks really weird. First... make a backup, then... Check all installed admin themes, disable, and uninstall those you don't use. Stick with the default for now. Do you use any other modules that change styling and or behaviour in the backend?

You forgot the screenshots.

New off-topic: The moment you remember you can easily disable mandatory fields in FormBuilder with just a few double-clicks and can finally stop entering data into 20+ fields. ??

How do you put the files on the server - FTP, SFTP, Rsync, Samba share or so? Do the access rights (read/write) of those files look ok? Is the session folder writeable?

So... at this point you, @BrendonKoz, and others should post all details about their setups to find the issue. Those warnings might not have an impact, BUT they are a very bad look when trying/installing ProcessWire for the very first time. For my current DEV-setups: latest DDEV (Host: Ubuntu 23.10, not virtual) PHP 8.2 MariaDB 10.4 Apache FPM InnoDB, utf8mb4 Latest successful ProcessWire version: 3.0.241 For my current PROD-setups: PHP 7-4 to 8.2 MySQL v. ??? on webgo, and whatever on Hostinger Apache - not sure how it runs there (webgo, Hostinger) InnoDB, utf8mb4 and a lot of MyISAM with utf8 and utf8mb4 ProcessWire from 3.0.165 to 3.0.241

Nothing like. Not even similar in the last couple of months. Even when installing it into an Nginx environment. And the worst part... not even a clue where to look. Is there more in the logs of either PW or Apache or Docker? Just installed a 3.0.241 (fresh download) a couple of minutes ago without issues (PHP 8.2, MariaDB 10.4 via DDEV).

That'a a core module. So it's in the /wire/ folder for a reason as it is part of ProcessWire itself. In this case you also don't download it, you just activate it. Nothing to worry here as well.

Ok, we have the same settings now. Besides mine is actually a Textarea (Multi-Language) field, but I don't think that's the issue here. I uploaded a short clip of how the field and/or frontend-editing now behave. It worked way better before. https://youtu.be/OOUKdEzH4Tc After all I maybe really just disable it again. As mentioned before I rarely use it and I have a quick link to the edit screen anyways.

I could support that statement, yet I now have worse problems than before and makes it totally unusable. I might missed something from your settings. Otherwise this is cursed. Can you post screenshots of your settings, please.

Until today I didn't know how burnt CPU cooling paste smells. ? I had enough fun for now with importing those datasets, time for the frontend shenanigans.

I am still not sure it this is a weird glitch or bug or maybe even expected behaviour. Until this very thread here I never really noticed any issues and didn't find any messed up articles so far, yet to be frank I rarely use that feature on a daily basis. I mostly enabled frontend-editing for some fields to clean up formatting, adding a sentence, fixing a typo, and similar tasks while browsing through the site. On the other hand I'm in the process of migrating some client projects over to Markdown textareas as those clients feel more comfortable using plain-text than HTML editors - and they just can't really f**k up things that bad in there. So it could become a concern when I enable frontend-editing there. It's not planned, but could be the case. @ryan , maybe you could give us more insights here? Is this expected behaviour or a weird glitch/bug?

I won't try to rebuild the NextJS version of it just to mimic every detail but build a usable app like it - don't know yet how every part will work and look. But for sure I won't load tons and tons of stuff just because something was in hover state or so. Maybe there is a reason for that but there wouldn't be one in my version of it - probably. I just want to see how nice and easy it could be to build such a tool and how fast it is at the end. As said before: I won't copy the app to the detail, I will try to build an app/tool that works and has all or most of the features. The most fun part until now was to realise that importing 50k items is something different than handling 50k items that grew over years. A nice reality check.

Couldn't resist and started playing around with it. What I can say so far: Importing 50,000 pages via ImportPagesCSV isn't the way to go I somehow remembered it to be faster and a bit more reliable even with such a large set of pages. Maybe I am wrong on this but I almost always use this module for CSV imports. wired together a custom import script Not all books and details where imported due to weird symbols/letters/words in the book titles and didn't bother fighting through that. ? I skipped almost everything on the first run and just created pages with titles. The database growth was kinda surprising for me. All that took less time, than trying to import everything with ImportPagesCSV. Those weird symbols/letters/words I mentioned earlier: Database difference pre/post import 50k pages with just the title: Created a public Github repo for this: https://github.com/acabelt/pwbookinventorydemo Feel free to play around with it. Added a working basic search function using HTMX and Twig Commit: bdf60d3 Will update this post with more details as they occure.

That sounds nice. I think. Could be fun. Doesn't Discord allow such things? If so we could go there. There is a ProcessWire channel already. However... love those Community Calls, Office Hours or how others call them.

That sounds great. Would it be the cloud-hosted version of TinyMCE then we would have in ProcessWire? If so GDPR could become a new issue and topic.

Changing the order results in chaos as the markdown will be shownas unrendered HTML - which is actually correct behaviour here and makes sense. I just removed HTML Entity Encoder, disabled Safe Mode, and played more. The result stays the same: at some point the textarea field or it's rendering becomes unstable and lots of <p> tags were added. Then I looked into the dev tools and saw that being in frontend-edit mode it outputs actually HTML and not real markdown - like it does in the admin. With CKEditor or TinyMCE fields it's fine and expected as those are WYSIWYG editor but here in Markdown it's not. Tested further and found that it is the same with real plain text textarea fields. It makes the rendered HTML editable and doesn't render the textarea as InputField like in the admin. Frontend: Backend: So... not perfect for plain text/markdown fields. I might be totally wrong here but it's either: Output Formatting or the fact frontend-editing doesn't load the real InputFields It's curious that I only ran into this problem because I tried to run into it. I use this for quite some time now, 3 months at least, and never noticed an issue. Maybe I should look into each and every page now. ??

Two things are different in our setups. HTML Entity Encoder is enabled Safe Mode in Markdown/Parsedown is enabled For both I can't tell why they are enabled. I guess it's the default setting. At least I can't remember changing that. Another thing is that I usually don't mix Markdown and HTML in my textareas. Just plain Markdown. This is important because the moment I try to fix the HTML in the code annotation that textarea starts become unstable. And only then. First it adds new lines to the code area, next it adds paragraphs everywhere - even in other list elements. Adding only Markdown without any HTML doesn't change the behaviour. And that's what I tried first. Something different but similar I noticed was that I can't set line-breaks/new lines from the frontend. Usually in the backend I add two spaces at the end of the line, hit enter and start a new line. That doesn't work in the frontend at all. It actually messes thinks up similar to your issue. Just an idea that came up: Could it be an issue with output formatting and that it is not working as expected in the frontend?

Ok, so after more playing around with the frontend-editing I got it to throw up - kind of. I threw in a code comment: ```twig <li> asdads </li> ``` And I got a totally messed up textarea/markdown back. Everything in new lines/paragraphs. Totally unusable. Went back to the admin, pasted in the old content. Everything was fine again. Tried again and nothing happened. Besides the code block looked a bit off, went into edit-mode and saw this: ```twig asdads ``` the <li>s were missing, cleaned that up, and got it to throw up again. It takes some tries here but once in a while something goes wrong. Tried different HTML tags but those <li>s or code blocks seem to cause issues when added from the frontend. Tried the same in the admin and everything was fine.

This doesn't look right. Maybe someone thought it would be a good idea but usually the other files (commented out) would be used here. However those _head and _foot are in /site/templates/includes/ therefore it's missing in your config. // should probably be this: $config->prependTemplateFile = 'includes/_head.php'; $config->appendTemplateFile = 'includes/_foot.php'; The new server throws errors that should be logged to /site/assets/logs/errors.txt. Do you have still access to the old version?

I'm using a similar setup with markdown and frontend-edit. Copied your snippet, added demo content, wrote text... no new lines added here. I put some screenshots here to compare. If you want, drop me one of your .md files and I will test with that.

Wouldn't this be an awesome demo of ProcessWire as well? Here is the original tweet from Lee Robinson (VP of Product @ Vercel) - links below: Lee/NextJS: https://x.com/leeerob/status/1822668486214140134 Josh/Laravel: https://x.com/joshcirre/status/1824227064184181150 Github: https://github.com/vercel-labs/book-inventory Demo: https://next-books-search.vercel.app/

I have had this in the past or at least very similar with a custom Debian-based Apache, MySQL setup I tried to run and manage myself. I don't know what I did wrong, but everything seemed a bit off. Since using DDEV, moved away from Laragon (Win) and MAMP (Mac), never had this issue anymore. The question to ask here is: Which system is off or needs a better config? Where is your live server from or who is your hosting company? If I had to guess... A2*, Dream*, or Blue*host - or something similar.

I'd support the "enterprisey" feel of Laravel and the whole ecosphere around it. Some of those big packages and starters aren't just a package with a README.md, they have full websites to explain what's happening - even those that are free (or not that expensive). I totally get that feeling, the vibe, the experience... yet it's way over everything I want to handle (aka my comfort zone). I did the 30-day-challenge to learn Laravel and I learned a lot. I learned to invest more time in ProcessWire as I am already familiar with it and could do way more with it, when investing more time to learn some new basics (modules, hooks, custom classes, and such). I love the simplicity of ProcessWire. From fields and templates, to selectors, to templating. You can learn all that in a weekend. While hooks and modules, custom forms, and more... may take a bit longer (weeks at least, for starters and non-PHP-Developers). Still... are there some things we could learn, should adopt, might take a look at from Laravel, or CraftCMS, or Symfony, or... I asked it myself, but I'm absolutely not the right person to ask those questions, so... here we are. ?

As I look at Laravel, and quite often stumble across YouTube videos about it, these days I asked myself... is there something that Laravel does (way better) that ProcessWire should/could/has to do as well? Things I find super interesting are those Breeze, Intertia, Volt, Livewire starters. Amazing! Or the Laravel Queues, those various database adapters to use SQLite or Postgres just by changing a line in the config. The Tailwind/Vite workflows, and things like that. Not to mention all those on-demand services. It's impressive! But sure, those are big and heavy things you can't just copy, but there is a reason people love Laravel. I know some of us here are actively using tools like Laravel and CraftCMS. Why? Both are super complicated right from the start aka installation. (yeah, I love to move around files and use my ZIPs to extract them into other folders and go from there!).

Don't tell anyone but 90% of my ProcessWire code consists only of if/else/foreach/echo statements - nothing more. You don't need more. That's all. My opinion. Ok, nowadays there is a bit more twig involved, and some hooks, and modules... yet not that necessary. Everything beyond that is some kind of voodoo-magic for me. On the other hand: this forum has almost all answers (for starters) already. If not, this community is the best and will help. So... We still have more options: exclusive (on Discord, in the newsletter, ...) short time only starter-price (+$50 every 100 sales) 30-day-money-back-guarantee