Webrocker Posted August 3, 2015 Share Posted August 3, 2015 Hi, currently I'm testing a rebuild of an 18yr old forum. basically it's a a pet project of mine, to get to know ProcessWire better, but I'm sure it could work, since the core functionality of the forums original script is fairly simple and the added functionality could very well be represented with the cms parts… For testing's sake I have imported the data of about 4000 users via the API, using a custom template file (by using the approach shown here: https://processwire.com/blog/posts/processwire-core-updates-2.5.14/#multiple-templates-or-parents-for-users ) with some additional fields with some meta data from the old forum's user settings. this worked out pretty good, only that I had to split the import in chunks of about 500 entries, b/c otherwise the database connection would time out (or maybe the php script runtime is/was to blame). now I have these users in my PW install, and viewing them via the pages tree is possible. but once I switch to the lister, the complete website will stall, front- and backend, and after some minutes a SQLSTATE error will be thrown: Warning: Error while sending QUERY packet. PID=10464 in processwire/wire/core/Pages.php on line 1992 2015-08-03 12:50:46 Exception: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away (in [...]processwire/wire/core/Pages.php line 1992) #0 PDOStatement->execute() #1 processwire/wire/core/Pages.php(477): Pages->executeQuery(Object(PDOStatement)) #2 processwire/wire/core/PagesType.php(258): Pages->getById(Array, Array) #3 processwire/wire/core/Users.php(29): PagesType->get(41) #4 processwire/wire/core/Session.php(96): Users->get(41) #5 processwire/wire/core/ProcessWire.php(259): Session->__construct() #6 processwire/wire/core/ProcessWire.php(84): ProcessWire->load(Obje 4000 entries shouldn't be a problem, or is it? I know that this is hard to tele-diagnose, so before going deeper into it, I wanted to ask if there are limits performance-wise on what the API can handle? I'm asking because we plan to use the PW backend with listerPro for a project where we expect 10.000 to 20.000 entries which should be search- and filterable in the backend. The above error will be thrown if I try to set a second filter besides the "template" like "forum_user" - in my testcase there's a "legacy_userlevel" field which is an integer and has values through the import of "-100","-1","0", "1", "2", "3". (that's only temporary, I plan to switch to roles based on those old settings). The lister tries to query this field in order to make a select input where I could then select one of those values… this times out. In the "forum_user" template fields I have no settings like "global" or "autojoin" or else… I'm on the ProcessWire 2.6.9 dev version and currently in "advanced" modus. Update: Even if I try to switch to "access" or "roles", the backend will time out. This started to happen with the addition of the many users… without altering the set up, everything worked when there were only the first twenty users. Even though I'm on a managed root server with this testing project, I suspect that the script settings may be a bit… sparse. What ini settings should I look out for to counter this error? cheers, Tom Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now