benbyf

You were totally right. I had to basically go over my config.php highlighting everything and deleting all teh whitespace and it worked, there must have been some rogue white space or strange invisible characters somewhere which VScode wasn't showing 😞 very aannoying and not something I've encountered (especially when I must have introduce the bug myself! 🤦‍♂️). Thanks!

mmm, not sure what you mean, there's nothing weird in the config. Here's the errors i get on the front for the site with Debug turned on: Warning: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent in /srv/users/serverpilot/apps/mysite/public/wire/core/WireSessionHandler.php on line 57 Warning: session_name(): Session name cannot be changed after headers have already been sent in /srv/users/serverpilot/apps/mysite/public/wire/core/Session.php on line 294 Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in /srv/users/serverpilot/apps/mysite/public/wire/core/Session.php on line 297 Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in /srv/users/serverpilot/apps/mysite/public/wire/core/Session.php on line 298 Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in /srv/users/serverpilot/apps/mysite/public/wire/core/Session.php on line 299 Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in /srv/users/serverpilot/apps/mysite/public/wire/core/Session.php on line 300 Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in /srv/users/serverpilot/apps/mysite/public/wire/core/Session.php on line 312 Warning: Cannot modify header information - headers already sent by (output started at /srv/users/serverpilot/apps/mysite/public/site/config.php:1) in /srv/users/serverpilot/apps/mysite/public/wire/modules/Process/ProcessPageView.module on line 105

Sometimes it lets me in but its a blank screen, with Debug on it errors with: Warning: Cannot modify header information - headers already sent by (output started at /srv/users/serverpilot/apps/mysite/public/site/config.php:1) in /srv/users/serverpilot/apps/mysite/public/wire/modules/Process/ProcessPageView.module on line 105 Warning: Cannot modify header information - headers already sent by (output started at /srv/users/serverpilot/apps/mysite/public/site/config.php:1) in /srv/users/serverpilot/apps/mysite/public/wire/core/admin.php on line 28 Warning: Cannot modify header information - headers already sent by (output started at /srv/users/serverpilot/apps/mysite/public/site/config.php:1) in /srv/users/serverpilot/apps/mysite/public/wire/modules/Process/ProcessLogin/ProcessLogin.module on line 311 Warning: Cannot modify header information - headers already sent by (output started at /srv/users/serverpilot/apps/mysite/public/site/config.php:1) in /srv/users/serverpilot/apps/mysite/public/wire/modules/Process/ProcessLogin/ProcessLogin.module on line 312 Warning: Cannot modify header information - headers already sent by (output started at /srv/users/serverpilot/apps/mysite/public/site/config.php:1) in /srv/users/serverpilot/apps/mysite/public/wire/modules/Process/ProcessLogin/ProcessLogin.module on line 313 not really sure where this data is stored or how it can be changed...?

No dice 😞

Hi! Sorry one of those perernial issues...-> moved to new hosting and some of the settings were obviously wrong as when hitting the view button while editing a page, it would link through to the page on the old hosting. I changed the host names in the config $config->httpHosts = array(...) and found I could no longer login without getting the forged notice. I cleared my cookies and deleted the contents of the sessions table in the db but no avail. Any advice?

Hi @gmclelland what version of PW? Just checked on PW 3.0.229 and seems to be fine.

Things I love: its not wordpress - mostly a security issue this one easily get CMS data and role your own php / frontend to display / do something with it... anything you can imagine modules making is approuchable (though could do with a good user guide as they're changed quite abit over the years) community is great! doesn't break, or need upgrading very often

So I did another install using the blank site theme and that worked so must have been a mismatch between the exported site and the database setup on both maybe? anything that can rectify that situation short of having the same environments?

Hi everyone, having a similar issue installing PW 3.0.229 or 3.0.244. getting lots of SQLSTATE issues on installation of custom site (using site export module). php 8.2.27, compatability check all ticks, errors using both innoDB and myISAM but differently.

working! thank you

yep I have both LazyCron.casche and LazuCronLock.cache both there... should i delete them both to reset??? I ideally want it to work as a module as its needs to be duplicated to other sites and not as a singular modele - e.g. you can install several times to repeat for different needs... also I've made it work in teh past which is mostly whats annoying me that it no longer works as ive previously done it.

I get messages turning up fine in my logs when used in my templates but not working (nothing happens) in my module for some reason. Here's what I have roughly: class customModule extends WireData implements Module, ConfigurableModule { public static function getModuleInfo() { return array( ... 'autoload' => true, 'requires' => "LazyCron", ); } private $cron_check = "everyMinute"; public function init() { // add hooks to CRON $this->addHook("LazyCron::every30Seconds", $this, 'checkFeedForNewPages'); } public function checkFeedForNewPages(HookEvent $e){ wire()->log->save('messages', 'working again'); } }

Is there any working example links at all?

Ha yeah I saw that, I thought it worked well together as the instant visual works with me brain :)