![]() ![]() |
May 23 2012, 11:18 PM
Post
#1
|
|
|
Newbie ![]() Group: Members Posts: 8 Joined: 10-May 12 Member No.: 1,189 |
Is this a documented bug? Can you reproduce? |
|
|
|
Jun 4 2012, 01:54 PM
Post
#2
|
|
|
Newbie ![]() Group: Members Posts: 8 Joined: 10-May 12 Member No.: 1,189 |
I see there's no feedback on this issue. It's really a big problem because if users are creating content on the site while the cron is run they are forced to re-login and loose their work!!!
Any comment will be very appreciated... Thanks! |
|
|
|
Jun 4 2012, 02:06 PM
Post
#3
|
|
|
Newbie ![]() Group: Members Posts: 8 Joined: 10-May 12 Member No.: 1,189 |
Well, desperately looking I found that logout line in the cron script that I removed and it seems to eliminate the problem. Wish it's not a security risk and that the created session will eventually expire by its own. Besides my concern is that a new session cookie be created every five minutes my script runs and could stall the server.
CODE if ($mainframe->login($credentials)) { $controller = new PostByEmailController(); echo $controller->importAll(); // @$mainframe->logout(); } else echo 'Post By Email Cron Job fatal error: the login attempt has failed, wrong username and/or password!'; Would still appreciate some comment from the developer, yet I had to alter that cron file in so many ways to have it work correctly! Thanks! |
|
|
|
![]() ![]() |
Similar Topics
|
Lo-Fi Version | Time is now: 2nd June 2026 - 03:03 AM |