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.

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

Upgrade 19.0.3 --> 20.0.1/20.0.3: Warning in upgrade2.php (Not allowed path) #32225

Open
SysUserR opened this issue Dec 4, 2024 · 4 comments
Labels
Bug This is a bug (something does not work as expected)

Comments

@SysUserR
Copy link

SysUserR commented Dec 4, 2024

Bug

When updating form 19.0.3 to 20.0.1 we get a warning during data migration.
Ref. picture.
dolibarr-error-message

Dolibarr Version

20.0.1

Environment PHP

7.3.33

Environment Database

MariaDB 5.5.5-10.6.5-MariaDB

Steps to reproduce the behavior and expected behavior

No response

Attached files

No response

@SysUserR SysUserR added the Bug This is a bug (something does not work as expected) label Dec 4, 2024
@hregis
Copy link
Contributor

hregis commented Dec 4, 2024

@SysUserR can you try with Dolibarr 20.0.2

@SysUserR
Copy link
Author

In my daily working system I am using Doliwamp for an upgrade (Windows PC).
There the described failure message is comming from.
I now upgraded my backup system (Windows PC) from 19.02. to 20.0.2 with the Dolibarr ZIP-file manually.
The described failure message comes up in the same way, so the issue is existing on two systems (in my case).

@SysUserR
Copy link
Author

I upgraded both systems with DoliWamp to V20.0.3.
On both systems I get the same warning like described above.

@SysUserR SysUserR changed the title Upgrade 19.0.3 --> 20.0.1: Warning in upgrade2.php (Not allowed path) Upgrade 19.0.3 --> 20.0.1/20.0.3: Warning in upgrade2.php (Not allowed path) Dec 30, 2024
@hregis
Copy link
Contributor

hregis commented Dec 31, 2024

@eldy @SysUserR i send a PR to fix this warning : #32494

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug This is a bug (something does not work as expected)
Projects
None yet
Development

No branches or pull requests

2 participants