flydev

Glad to hear that 👍

Hi @Claus Don't worry, you SHOULD do it before doing something else 🙂 Duplicator will not alter anything, still. --- Whether local or live, it's always recommended to make a copy to avoid any frustration. Duplicator will me a perfect copy of your live site and you will have possibility to either download the backup (package) from the admin page or manually from your FTP server. Inside the package you will have at hand your distant database backup and all distant files (based on the configuration -> see module's settings - using default settings is safe). So if your goal is to update your local dev, then you must (as always) make a backup of it just in case. Once that's said proceed following theses steps: make copy of your local dev create a backup on live site and download the package update your local dev site - here you have two options as I don't know how your local setup work: option 1 (manual): extract the zip and import your database then adjust database settings in config.php file to use your local database server. option 2 (auto) : use the installer.php and follow the steps to import everything Now, if you need to bring back modifications from the old dev (local) site to your new dev (based on fresh live site) then you have to do it manually. Using a diff tool make thing easier and faster. Using @bernhard migration is also a good option.

@bernhard I didn't found a thread about Consenty so im writing here. Are you wiling to accept a PR about making Consenty as node.js module? Creating a npm account isn't necessary as we can install libs from github. It wouldn't change nothing for people grabbing the minified file but it would be easier for installing and using it for people building apps using npm or yarn or whatever. I just realize that consenty isn't a pw module and I should have opened an issue on github 😅

you will find on the forum and internet a lot of threads about getting started on pw. There is one nice guide made by a big company I like to quote since: https://www.ionos.com/digitalguide/hosting/cms/processwire/ ps: nice move 🤙

Hi @Laegnur I suggest you to use @nbcommunication Cloudflare turnstile module if it’s a valid option or @MoritzLost hCaptcha module as my module was not updated for a while, see: —- ps: you can get an introduction on https://weekly.pw/issue/542/ —- About the hook I writen above it may still work, but you have to debug it a bit. The issue you described seem to happen in verifyResponse() check your dev console by checking `Preserve log` on network tab to be able to check whats going on after a page reload.

About the logs they are generally located in /public_html/error_log or /logs/example_domain_com.php.error.log The database is not altered, the instaler basically just import your database backup file as is. Yeah, logs would help, but I will try to setup a muti-site instance to see how it work. I know the installer is also looking for the hardcoded `site` location.

Just a small note, if wirecli is installed globally, then to update it to the latest version, just type: composer global update wirecli/wire-cli

Thats make sense then. I think we never had this case and as I never used this setup, we can assume it's not supported (you spotted the constant). I am interested to get the log from the server that you can get on the CPanel. I open an issue on github, I will test it. edit: @MarkE what is the version of PHP ? edit2: I tested backup and restoration on a package of 600MB on php-8.2, no issue so far. Yes ok, renaming to `site` should work if no hosting memory error is raised, which is common on those webhosting.

Hi @MarkE there is no stupid question as they help others dev to get the right answer when they search for it. What’s the type of hosting? Webhosting or you have your hands on the server? the error seem to be due to the size of the zip as it say the object is not initialized, but I might be wrong, and about the native method, maybe its an issue with the zip extension. Please check the logs of the server and duplicator. edit: I suggest you to try with small setup, I mean you exclude some folders from the backup to get a smaller package just for testing.

quite biased message Just my two cent's here. I tend to say - yes - just because I see third-party app/websites as a nice showcase on how pw can handle things and how versatile it is. I must admit that on my side I am using pw as second choice for a simple reason, I write websites in pascal (I can remember @LostKobrakai switching to Elixir). But, it's only depending on client needs and profile, and maintainablity. If a client absolutly require a setup based on php to be used with a standard web hosting, then pw come back as the first choice with no doubt. This piece of software is solid and deserve to power thoses tools made for processwire. I would have felt disappointed if weekly.pw was made as static website or worst, on wordpress, imagine. The real decison maker is I think, money. Domain names are more expensives then ever. About hosting, there is a lot of solid companies providing such web hosting, generaly you got 100MB free for ever on OVH or Alwaysdata (the second provide ssh access). For the domains fee's, the community could make some donations. It could be made using built-in page json feature with or without inertiajs and consumed from AstroJS, keeping ci github flow without any problem to let the community collaborte on it. You will won the right to add on the footer "powered by processwire" 🫡😄

Just throwing what I am used to work with: monitoring: uptimeflare as status page, customizable and it work with cloudflare workers (not self-hosted as is, but can be done with cf wrangler). goaccess for a deep and nice views of web logs. really, this is a must have. prometheus for all sort of metrics and creating charts for visualization (I dont use it but a self made metric server for the same purpose. but with a plugin for goaccess). pulseway: (commercial) for notifications via custom app (api is available), mail, mobile push based on pulseway's agent features, goaccess / uptimeflare / "prometheus" or whatever. Vesta control panel: for easy web-hosting management (to be used only on a vpn - dev recently resumed and v2 is on the pipe). umami: for web analytics. OpenVPN: can't live without it, For you and/or clients. Deployed in a minute and it's a matter of seconds of adding/revoking clients. I must add here that custom gui can customized easily. Fossil: an advanced but simple SCM Invoice Ninja is really cool because of their desktop and mobile apps, despite the UI which could be improved a lot. it's a matter of tast for sure. I knew it from Firewire here inthe forum. Just a note about files and synching (de-google): since two years or so, I only deploy Synology NAS with synology drives among others tools available from it. No more files lost, management is easy for self or clients infra, and is highly configurable.

Hello guys. If you get a “Collation unknown” error, it's probably because your MySQL server version is earlier than 8.0.1, i.e. your dev/staging/prod servers are not the same (I suggest you harmonize and work on the same servers to avoid potential problems). You can consult the mysql documentation on collation migration: collations-migrating-from-older-collations If you'd like to go further in understanding the collation naming suffix, take a look at the table in the mysql documentation there. (I take a note about the installer file; You can give a read to my comment here too for notice type meanings).

It was the goal by insisting a bit, glad it work and cheer on you for not surrendering ?

I just suggested priority in case there is another hook somewhere of even to not let the system decide when to call it as we have not a profiling report, just set a priority highter, it doesn't hurt to make a test. Also, the reason of why I posted the issue is because I am assuming from your screenshots that you are not making tests with root user id (#7815), so you should test with root user on both envs in order to tackle in first instance the permission issue you posted in your other thread, and post the results.

You didn’t told us what’s the result if you set / change your hook priority. edit: and are you 100% x 3 sure that roles and permission are the same on both envs ? edit2: (again ?) profiling your code will give you more skills than copilot, and loose less time on this whole thing. edit3: you should read this issue to see if it help about what are trying to achieve: https://github.com/ryancramerdesign/ProcessWire/issues/302 edit4: what the bot say: The issue could be related to the priority of hooks and the sequence in which they are executed. In ProcessWire, hooks can be attached in different methods such as init()and ready(). The init() method is called before ProcessWire handles a web request, while the ready()method is called after ProcessWire determines what page is going to be viewed but before the page is rendered. If the module ready is called earlier, it might affect the sequence in which hooks are executed, potentially leading to the observed issue. To solve this issue, you can try the following steps: Ensure that the hooks are attached in the correct method (init() or ready()) based on when they need to be executed. Adjust the priority of the hooks to control the order in which they are executed. Additionally, you can use the standardized include/hook files provided by ProcessWire: /site/init.php: This file is included during ProcessWire's boot initialization, immediately after autoload modules have been loaded and had their init() methods called. This is an excellent place to attach hooks that don't need to know anything about the current page. /site/ready.php: This file is included immediately after the API is fully ready. It behaves the same as a ready() method in an autoload module. The current $page has been determined, but not yet rendered. This is an excellent place to attach hooks that may need to know something about the current page. By ensuring that your hooks are placed in the appropriate files and adjusting their priorities, you should be able to resolve the issue with the listable status in the live environment.

@adrian I applied fixes you reported earlier. I also merged changes from the dev (stable as today - v1.5.4) into the feature-encryption branch, this last is not ready as I need to re-read the whole conversation I had with @netcarver in order to finish it, but it works, just in case you want to test it. FYI, the v2 is also in the pipe and coming with a dedicated software to manage the process between all your websites from a centralized desktop/mobile app. It might will be part of a paid feature, still not decided.

@szabesz actually the bot do not contain all the data I want, there is something like 5k rows of data, and to achieve it I need to scrap almost all the forum. Even if the process is not resource consumming there might be something else, It doesn't hurt to ask first.

Thanks @howdytom! I just answered on your github issue. Just in case you are not aware of, you can also find a Pro module made by @ryan that use mainly htaccess to kill bad bots. The Pros of RequestBlocker that is a Cons in Blackhole is the fact that agressive bots could degrade the server resources. sort of denial of service. Anyway, when used for example, behind a well configured reverse proxy or a service like cloudflare, the cons is really mitiged.

Didn't you feel like you were reading a comic book, because it looked so easy and the code is so well written/commented? Ryan is so skilled you quickly realize that the tool is robust lol Just played with a chatbot that will be soon publicly available (need to ask ryan and mods) with some @MarkE text chunk from this thread :

but but but we told you to try with the same env, anyway glad to hear it's solved, this type of issue kill a kittie each day.

Yes, in the first screenshot it show the two output files generated by xhprof and the second is a diff tool to compare the two files. Using a diff tool make easier to see the differences at a glance.

@MarkE I read the other posts, I do not see any code chunk about how you are calling your hooks. As you said it's working on /site/init.php .. .. you have to remember that calling hooks implies also a context, I mean $wire/wire() vs $this, just a thought. Please confirm / insert coin ? edit: And you might also test hook priority option, check there: Edit 2: I made you a small preview of a diff running debug true vs false, on a almost blank website, there is only one user modue installed:

@MarkEby reproducible example I mean we could reproduce the issue. You could for example just publish/paste your module structure without all the business logic. Without code it’s not easy to help in this case. Without insisting, profiling your setup will speed also the debug process, as you will see instantly when your module is initialized and maybe also spotting where the glitch happen between the dev and prod. Maybe we are also going too far and might be a simple permission issue. Idk.

Also, when you say it isn't working on live environment and everything is identique, does this sentence imply $debug is set to true and tracydebugger is enabled? Just asking as it make the env not the same, and then hooks order is likely not the same. To make things easier, publish or send via pm a reproducible example ?