flydev 👊🏻

Hi, first of all, make a backup of everything. About the issue, it look like you have 2 modules file for the Fieldtype Repeater. One in wire/modules and another one in site/modules. Did you modified intentionally the module and made a copy of it in your site/module dir ? If yes, then do a Modules > Refresh then select the right Repeater module you want. If NOT, then rename the site/modules/Fieldtype/FieldtypeRepeater/ to site/modules/Fieldtype/.FieldtypeRepeater/ (note the dot before the module name) and do a Modules > Refresh. (it's quite strange, maybe a bad upload moment from you.)

Hi @Orkun Your data are sampled for 1 second, it's unusable. Try to visit your culprit page, wait its finish loading then run the SQL command. Post your result once you get sampled data for 20-40 seconds.

How much page contains the system ? You could try to spot the issue following these blog post : https://www.chriscalender.com/using-show-processlist-and-mysqladmin-debug-output-in-conjunction-with-show-innodb-status/ https://www.chriscalender.com/advanced-innodb-deadlock-troubleshooting-what-show-innodb-status-doesnt-tell-you-and-what-diagnostics-you-should-be-looking-at/ About AdminThemeUikit slowing down the system, i see no reason here.

Hi @dragan sorry for this late answer. Yes the vendor folder need to be uploaded and do not need to be moved elsewhere. As a quick fix, you could try to remove the HookEvent type from line 175 : https://github.com/flydev-fr/OAuth2Login/blob/master/Oauth2Login.module#L175 Let me know if it worked, else I will test it at the end of the day, thanks.

Hi, you should consider adjusting innodb_buffer_pool_instances and innodb_buffer_pool_size : How much memory is available on the server ?

Hi @sodesign , interesting, did your issue is fixed ? if yes, how ? thanks; And to answer the two questions : Yes, but it should only do that if you tell NGINX to do it. About the issue, and based on your post, it look like a cache issue where cookies has been cached. The official statement say that by default, NGINX respects the Cache-Control headers from origin servers. It does not cache responses with Cache-Control set to Private, No-Cache, or No-Store or with Set-Cookie in the response header. This is the current behavior; I will add that before the version 0.8.44, the header was stripped then the request cached. All that to say that theses parameters can be overridden, and you should show us your NGINX config file before we go further.

So yes, the credentials are shown on the terminal of the VM at the end of the install : credentials in yellow

mmmh ok, downloading and trying, stay tuned 🧐 And what give this command-line ? sudo cat /home/bitnami/bitnami_credentials

Generally the username and password are shown on the terminal, on top of the shell in the disclaimer at the end of the installation typically giving you the scheme, IP and the credentials. Try user as username and bitnami as password. Edit: https://docs.bitnami.com/virtual-machine/faq/get-started/find-credentials/

My bet, it's spam, they are totally trying to extorque bitcoin. It look like an automated message. And from what we can read from there on Internet, they are sending this message to owners of google blogs 😂 and we know that for hacking a google blog, they require your google account, which I doubt it was hacked. Anyway, you can look at your file structure, DNS records, etc to see if something is weird but in every case, DO NOT PAY 👍🏼 I am quite confident to say that your are still safe 🙂 make your best poker face 😅

What @teppo said, also, what is returning error or response ? Admin markup ? If yes, you might need to set the Content-Type header. Can you post your request headers here ? What is /post/ ? Can we see a chunk code ?

Today, I am glad to announce that the module support the native image field 👍🏼

Do you have withCredentials: true in your app config or in your request ? Without it, cookies are not saved.

Screencast updated - import of an entire article ☝🏼️ Still dealing with media files.

Hi @joer80 In the top of the post.php file, you can write your logic to check which user is allowed to post or not xhr request. Example : <?php namespace ProcessWire; // if the page is viewed wihtout ajax, return if(!$config->ajax) return; // if the user is a superuser, return if($user->isSuperuser()) return; // only editor can post request to this page if(!$user->hasRole('editor')) return; // other checks if needed, CORS check, Custom header check, etc // rest of code - access granted // ... then, for example in your component , but anyway you already know how to do it : // example editPage() { this.$store.dispatch('setEditPage', this.$route.path).then(() => { axios .post(config.apiEditPageURL) .then(response => { this.data = response.data }) .catch(error => { this.errored = error }) .finally(() => { this.$store.dispatch('loading', false) }) }) },