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

ps_metrics issue #776

Open
musicpanda opened this issue Sep 18, 2024 · 4 comments
Open

ps_metrics issue #776

musicpanda opened this issue Sep 18, 2024 · 4 comments

Comments

@musicpanda
Copy link

An annoying warning within Prestashop 8.1.7 that has been around for more than two years:

Warning on line 2292 in file /home7/bocxas/trendyshop/classes/module/Module.php
[2] file_exists(): open_basedir restriction in effect. File(/views/templates/hook/HookDashboardZoneTwo.tpl) is not within the allowed path(s): (/home7/bocxas/:/opt/cpanel/eaxphp81/root/usr:/usr/local/lib/php:/tmp:/etc/pki/tls/certs/ca-bundle.crt:/var/cpanel/php/sessions:/usr/local/bin/wp)

According to the Prestashop Github (PrestaShop/PrestaShop#30531) this is an issue that is caused by the ps_metrix module.

The suspect is the ps_metrix.php file. It contains twice the code
return $this->display(__FILE__, '/views/templates/hook/HookDashboardZoneTwo.tpl');

I suspect this is one '/' too much and that it should be:
return $this->display(__FILE__, 'views/templates/hook/HookDashboardZoneTwo.tpl');

@musicpanda
Copy link
Author

NB: you see this error immediately after you log in. Debug mode should be enabled and the server should have open_basedir set.

@fox-john
Copy link

Hello @musicpanda !

Thx for this report. We have publish a new release of Metrics (4.0.6) on Addons Store. Can you try to install this version, and say me if your problem persist or not ?

@intraordinaire intraordinaire changed the title ps_metrix issue ps_metrics issue Sep 19, 2024
@musicpanda
Copy link
Author

Hello @fox-john !

No, that does not solve the problem.

@fox-john
Copy link

@musicpanda ok thank you.

We will investigate the issue further, and attempt to apply a fix later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants