dragan

Found the culprit: I updated Admin On Steroids from 1.5.8 to the latest version and everything's fine again.

This only shows you the original HTML code. You have to open up the inspector to see the rendered code. Also, you can do CTRL + SHIFT + F in Chrome to search across all files (HTML, JS and CSS).

https://www.google.ch/search?q=ckeditor+bug+copy+and+paste+from+word It seems like there are many others encountering that same bug. Someone here e.g. suggests to only use "basic HTML" instead of "full HTML" https://www.drupal.org/project/drupal/issues/2940054 https://github.com/ckeditor/ckeditor-dev/issues/595 ^ seems like pasting on mobile browsers is/was also an issue...

I see a strange bug with some inline-styles, apparently set by JS: min-height: 364px (value depends on screen width). This is with today's dev version downloaded / upgraded. Text field and textarea containers are way too big! <div class="InputfieldContent uk-form-controls langTabsContainer" style="min-height: 462px;"> Does anyone have an idea where this is coming from? Does anyone else see this? (latest Google Chrome, Windows).

@Macrura I just installed your module / inputfield for the very first time, on the latest PW dev, and it simply doesn't work (only tried it with images so far). My settings are in the attachment. When I have it like that, I get the following error when I want to edit a page: Error Call to a member function size() on boolean Source file File: C:/xampp/htdocs/processwire-dev/site\modules\InputfieldSelectize\InputfieldSelectize.module(118) : eval()'d code:2 I tried it with the default theme and Uikit as well. Do you see anything wrong in the settings? The fields are all there in my template, and the code is directly copy and pasted from one of your original posts in this thread. The full error (with all system variables etc.) is here: https://drive.google.com/file/d/1mF4ZkWNe7hE8oZULqLUZmFMddv8nCOr5/view?usp=sharing (image too big to upload in the forum) Thanks!

It's most definitely possible. Good to know: PW uses PHP namespaces since version 3. https://processwire.com/blog/posts/processwires-roadmap-in-2015/#pw-3.0-changes-namespaces https://processwire.com/api/coding-style-guide/#3-namespaces

wow, PW is really going places ? I'd try with SHIFT CTRL V instead of CTRL V.

Moving a PW site is a breeze, even without any special tools. Here's how: https://processwire.com/docs/tutorials/installation-moving-and-troubleshooting/

You know, just because you have these settings in place, doesn't mean your host will actually allow / activate it. Most hosting providers have some sort of limits that you can't override. Do you have the same site installed locally? If so, do you see the same error 500? (with the same settings as in php.ini)

Why would you want this? What are you trying to accomplish? Apparently it's possible:

Well, you didn't tell us what you have tried. Did you try any of the suggestions of the a.m. thread? safe_mode, mod_security, increasing memory limit, check if GD library is installed, maybe upgrade PHP, what do you see in /site/assets/logs/errors.txt? etc.

But only within the same hierarchy (siblings) ?

You might want to use the functions API (just literally discovered it myself seconds ago...) https://processwire.com/blog/posts/processwire-3.0.39-core-updates/#new-functions-api

my bad, of course searching before posting would have been more clever - I found it: https://processwire.com/blog/posts/processwire-3.0.39-core-updates/#new-functions-api

I'm actually more confused about an apparently new (to me) way to use the API... I've never seen code writen like this before: $home = pages()->get('/'); // instead of $home = $pages->get('/'); I see in the config file $config->useFunctionsAPI = true; Is that the reason? Do you happen to know when this was introduced or announced? Can it do certain stuff faster/better or different than the old-school PW API syntax?

I've never used pagefileSecure, but you could try temporarily to add permission with $permissions->add("name") or similar.

Did you use the multilanguage site profile when you installed PW? There's a piece of example code you could perhaps adjust and use. https://github.com/processwire/processwire/blob/master/site-languages/templates/_main.php#L65 or... what tpr said, that's probably more what you need

@adrian If you use the custom Google search in my sig, you'll find a lot of nginx forum threads. One of the oldest is this one, with Ryan chiming in with tips... https://processwire.com/talk/topic/275-processwire-on-nginx/ @jturley Likewise, searching for "bad gateway" or DigitalOcean, you'll find a few other forum posts - some of them mention some special, problematic mySQL versions, others point to some special DB configs...

Did you clear the module cache? Maybe also logout / login again.

That works if you choose the %= selector (SQL Like) https://processwire.com/api/selectors/#operators

I guess that a chat channel would simply mean too much distraction. imho, there's nothing wrong with using a forum as the main place of communication, even in 2018. The general expectation with chat is that there's always someone around within 3 seconds with a useful reply / solution / answer. IRL it doesn't always work like that, if you have a day-job and have to focus on your daily work at hand. This may sound like I'm all against having a PW Slack channel - I'm not. But I'm simply afraid that infos / tips would be even more fragmented that way. (just my 2 cents)

"waiting for table level lock" would suggest that something is odd on the server side and/or mySQL. Maybe mySQL doesn't have enough memory, or is being re-booted every now and then, and can't handle the queries fast enough. Perhaps switching from myISAM to InnoDB would help already. Or maybe this is being caused by a large mysqldump process https://superuser.com/questions/1093610/mysql-5-7-stuck-forever-waiting-for-table-level-lock

oh, the author simply moved the new version to another, newer forum post, that's all (afaik). Here's a recent PW community-site (with a nice retro touch) btw, maybe you can get some ideas or inspiration there

PW runs potentially slower when debug mode is on I guess. Did you disable it in your tests? There are quite a few big sites and web-apps (even multi-site environments) built with PW. Perhaps at some point, no matter what framework you're choosing, you'll need to tweak and optimize at some point. I'm sure it will only be a matter of time until @bernhard chimes in here and tell you about the wonderful RockFinder SQL module he built. Some "native PW" queries were dramatically faster when using that module. Just one of many examples what you can do if you want even more speed. re: ProCache So far, I haven't had the need for this, but I only keep hearing good things about it. FWIW, here's a related forum thread And finally, there's also some "best practise" stuff worth knowing, like (chosen randomly):

I don't know either, since I never used .local. But try to add localhost or 127.0.0.1 to your site/config.php file in the "allowed hosts" array. And maybe also delete everything that's inside site/assets/cache and reload everything.