Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

weird error e107::unserialize() Parser Error #2990

Closed
Jimmi08 opened this issue Jan 20, 2018 · 2 comments
Closed

weird error e107::unserialize() Parser Error #2990

Jimmi08 opened this issue Jan 20, 2018 · 2 comments
Assignees
@Moc
Labels
status: testing required Someone needs to confirm this issue's existence and write a test to prevent the fix from regressing. type: bug A problem that should not be happening
Milestone
e107 2.2.1

Comments

@Jimmi08
Copy link
Contributor

Jimmi08 commented Jan 20, 2018 •
edited
Loading

dimante have site where xml import did weird things, So I asked for user account as admin.
And I ended with this error. But original mainadmin (first) doesn't see anything like this.

image
Only not familiar message is this one:
Undefined index: SERVER_ADDR, Line 174 of C:\inetpub\wwwroot\e107_JMG_DEV\e107_handlers\iphandler_class.php
@Jimmi08
Copy link
Contributor Author

Jimmi08 commented Jan 20, 2018

If I check Correct Permission in Tools, I get this error:
Failed applying filemode '755' on directory '../' -> the directory '../' will be skipped from recursive chmod Failed applying filemode '755' on file '../cron.php'`

@Moc Moc added the type: bug A problem that should not be happening label Mar 5, 2018
@Moc Moc added this to the e107 2.1.8 milestone Mar 5, 2018
@CaMer0n CaMer0n modified the milestones: e107 2.1.8, e107 2.1.9 Jul 18, 2018
@CaMer0n CaMer0n modified the milestones: e107 2.1.9, e107 2.2.0 Aug 22, 2018
@Moc Moc modified the milestones: e107 2.2.0, Future Feb 1, 2019
@Moc Moc added the status: testing required Someone needs to confirm this issue's existence and write a test to prevent the fix from regressing. label Feb 1, 2019
@Moc Moc self-assigned this Feb 1, 2019
@CaMer0n CaMer0n modified the milestones: Future, e107 2.2.1 May 22, 2019
CaMer0n added a commit that referenced this issue May 22, 2019
@CaMer0n
Issue #2990 - unserialize BC fix.
6849a47
@CaMer0n
Copy link
Member

CaMer0n commented May 27, 2019

@Jimmi08 @Moc I believe this one has been fixed. Hopefully it doesn't break other prefs.

@CaMer0n CaMer0n closed this as completed May 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Moc Moc

Labels
status: testing required Someone needs to confirm this issue's existence and write a test to prevent the fix from regressing. type: bug A problem that should not be happening
Projects
None yet
Milestone
e107 2.2.1
Development

No branches or pull requests
3 participants
@Moc @CaMer0n @Jimmi08