Jump to content

netcarver

PW-Moderators
  • Content Count

    1,828
  • Joined

  • Last visited

  • Days Won

    35

netcarver last won the day on November 17 2020

netcarver had the most liked content!

Community Reputation

2,704 Excellent

About netcarver

  • Rank
    Code Monkey

Profile Information

  • Gender
    Male
  • Location
    UK

Recent Profile Visitors

14,171 profile views
  1. @Confluent Design Nothing amazing I'm afraid, you'll have to edit the included CSS file (InputfieldStreetAddress.css) - or override the selectors it uses with your own in another CSS file that gets loaded later.
  2. Update: Found out why LazyCron stops working sometimes. Have added an issue for the fix here. If you are using PHP7 or above, you can improve the reliability of LazyCron by wrapping your hook in a try {} catch (\Throwable $e) {} block. (Note the catch - it's a \Throwable, not an \Exception, so it catches errors as well as exceptions.)
  3. If I needed that spec, cheaply (ie. self-managed), I'd consider Contabo's cheapest plan at ~Euro5/month + tax. Otherwise I've never had trouble with Digital Ocean's droplets or Hetzner's VPSs but the prices are much higher for that spec (US$40/month + tax on DO and ~Euro15/month for Hetzner + tax.) You didn't mention your bandwidth requirements so you'd also need to look at what's included in those plans and budget accordingly.
  4. @Marco Ro Can you expand on what you need from your hosting? Are you looking for something managed, self-managed, shared or what? Do you need to be in a data-center in a specific region?
  5. There is a module that does something a bit like this already.
  6. @PWaddict Which log file did you spot that in? Also, you can try the ProcessDiagnostics module as it has a DB helper that can run table repairs. You should always back up the DB first though before any operations like that.
  7. This sounds like an API bug, is it worth reporting this as an issue as well?
  8. @ryan Not sure if small requests count here in this storm of idea goodness. Please could you make ProcessLogger::formatLogText() hookable?
  9. If you think you've found a bug in WireDatabasePDO, please do open an issue for it in the processwire-issues repository.
  10. You'd know if your processes were forking as you'd be doing it yourself, or running software like php-resque that does it for you, so what I described above probably isn't the cause in your case.
  11. @monollonom If you are using ProcessWire's database (ie $this->database, wire('database') or wire()->database depending on context) then yes, it should connect again on the next query. What might be more interesting is trying to find out why the MySQL server is going away. Do you have any processes (like your API stuff) that are forking by any chance? If this is the case, the code in the forked process gets a copy of the parent state - including the pdo driver state - and when the child process uses that state to access MySQL, the DB server can close the connection, leading to "2006 MySQL server has gone away" for both the child and the parent processes. I discovered this running PW-bootstrapped code from forked PHP processes in some of my own installations where I have background workers processing various jobs. I do not know for sure why MySQL closes the connection, but my working hypothesis is that it closes it when it sees it being accessed from a different process ID. The cure, however, is fairly easy in these cases as you just make sure the first thing your forked code/background worker does is close the db connection - forcing the child process to create a new connection on the next database call which it then uses for the remainder of its operation, and leaving the parent process' connection intact and operational as well. Taking this action in my forked code totally cleared up these "2006" errors for me.
  12. @muzzer Nice find, thanks for posting about it. Please could you add an issue to the issues repo for this.
  13. Hi @Adam I upgraded a live site to the new version and, unfortunately, the update causes a 500 internal server error on PW 3.0.148. I suspect you might need to add a PW version check before calling the parent init() function. I've verified that it's the changed line by commenting it out and the module then functions properly again.
×
×
  • Create New...