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

Changing manager theme from default causes error #7

Closed
MokoJumbie opened this issue Mar 8, 2012 · 4 comments
Closed

Changing manager theme from default causes error #7

MokoJumbie opened this issue Mar 8, 2012 · 4 comments

Comments

@MokoJumbie
Copy link

This may not be specific to MIGX, but I can't find anything else which causes the error yet.

I created a new manager theme directory to customize the login logo. the only files copied over were login.tpl and a new image to which it referred. there is nothing else in the new theme directory. all other files are supposed to inherit from the default theme dir.

...but I get this error 'Fatal error: Uncaught exception 'SmartyException' with message...' when I try to edit a MIGX item after changing the theme. I was able to work around it by reverting back to the default theme.

@Bruno17
Copy link
Owner

Bruno17 commented Mar 20, 2012

does this fix this issue?
35942ef

@MokoJumbie
Copy link
Author

It doesn't seem to fix the issue for me, I'm afraid. At least, I can't tell if it does, because I am getting a series of different errors now:

Notice: Undefined index: sourceFrom in myhomepath/core/components/migx/model/migx/migx.class.php on line 137

Notice: Undefined index: renderer in myhomepath/core/components/migx/elements/tv/input/migx.class.php on line 81

...and this is with the default theme enabled, so it may be a different issue entirely. Note that I am currently using the nightly from the morning of March 24th.

@NunoBentes
Copy link

I´m having the same problem!!! Any solution for this issue?

@jaredloman
Copy link

For what it's worth, I was having this issue with the default manager theme when developing on my localhost which would lead me to believe it has something to do with server configuration. As to what exactly needs to be changed...I have no idea, but maybe that will give you a start in the right direction troubleshooting.

-Jared

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

4 participants