I upgraded to smarty 2.6.8 because of a security problem with 2.6.2. When I upgraded to this version it broke some of our developers code. Here is the problem: Warning: main(/usr/lib/php/Smarty/core/core.load_plugins.php) [function.main]: failed to open stream: Fatal error: main() [function.require]: Failed opening required '/usr/lib/php/Smarty/core/core.load_plugins.php' (include_path='.:/usr/lib/php:/usr/lib/php/Smarty:/usr/lib/php/XML:/usr/lib/php/PEAR') The problem is that the above core directory no longer exists. Instead there is an internals directory in it's place. What has happened here, and why is it still looking for a core directory? This isn't hardcoded in our developers code anywhere. I was able to band-aid the problem by creating a sym link to internals named core, but this is a workaround. What broke here? Reproducible: Always Steps to Reproduce: 1.Install Smarty 2.6.2 using emerge 2.Check for /usr/lib/php/Smarty/core 3.Install Smarty 2.6.8 using emerge 4.Check for /usr/lib/php/Smarty/core Actual Results: The core directory has disappeared. Something is still pointing to this directory however. Expected Results: The directory should not have been removed. If the path needed to change then everything pointing to it should have also changed.
Looks like this was changed in 2.6.6, I'll have a look at it tonight.
Make sure you clear out your templates_c and cache directories, this is probably what is causing this error: http://www.phpinsider.com/smarty-forum/viewtopic.php?t=4519&highlight=core+internals
Looks like it has refreshed the cache already clearing up the issue. However, it might be nice to have the ebuild mention this step if it can't handle it automatically.
I just added it to the smarty-2.6.9 ebuild which was commited to cvs earlier on today for (yet another) security fix.
