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

Smarty error after update (versions later than .32) #711

Closed
Kissaki opened this issue May 13, 2009 · 4 comments
Closed

Smarty error after update (versions later than .32) #711

Kissaki opened this issue May 13, 2009 · 4 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.

Comments

@Kissaki
Copy link

Kissaki commented May 13, 2009

If I upgrade from .32 to one of the 3 newer versions, after the db update,
my xoops site, which uses smarty as well, will exit with an error:

"Fatal error: Cannot redeclare class Smarty in [...]/piwik/libs/Smarty/Smarty.class.php on line 65"

Running .32 it does work however.

@robocoder
Copy link
Contributor

I don't recall any Smarty changes since 0.2.32.

Can you remove your Smarty tmp/ folder and recreate it?

@Kissaki
Copy link
Author

Kissaki commented May 14, 2009

I did (re)move my old piwik folder entirely, just keeping/copying the settings file.
Thus, the tmp folder was entirely empty before first use/upgrading db.

@Kissaki
Copy link
Author

Kissaki commented May 14, 2009

Or do you mean empty the tmp folder after the db update again?

@robocoder
Copy link
Contributor

Sorry, I'm out of ideas.

I'm going to close this ticket as it's an integration issue outside of Piwik but invite you to post on the forum and see if other xoops users can help.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Projects
None yet
Development

No branches or pull requests

3 participants