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_Resource::parseResourceName incompatible with Google AppEngine #22

Closed
brandomeniconi opened this issue Apr 2, 2015 · 1 comment

Comments

@brandomeniconi
Copy link

Google AppEngine PHP Environment uses paths like:

/base/data/home/apps/s~[project-name]/[module]:[version]/[path]/template.tpl

example:

/base/data/home/apps/s~myproject/default:1.316876871687/templates/template.tpl

The function Smarty_Resource::parseResourceName in libs\sysplugins\smarty_resource.php uses this code to determine resource type:

   public static function parseResourceName($resource_name, $default_resource)
    {        
        $parts = explode(':', $resource_name, 2);
        if (!isset($parts[1]) || !isset($parts[0][1])) {
            // no resource given, use default
            //...

and when we have this type of path, the explode(':' splits the $resource_name incorrectly.

It's possible to change the delimiter or escape the path?
Thanks

@brandomeniconi brandomeniconi changed the title Smarty_Resource::parseResourceName incomaptible with Google AppEngine Smarty_Resource::parseResourceName incompatible with Google AppEngine Apr 2, 2015
@uwetews
Copy link
Contributor

uwetews commented May 4, 2015

The fix is now in dev-master and will later be included in version 3.1.22

@uwetews uwetews closed this as completed May 4, 2015
think-mcunanan pushed a commit to think-mcunanan/smarty that referenced this issue Mar 22, 2023
…変更に対応する (smarty-php#22)

* used sub query and converted sync_kanzashi_enabled_staff_reservation_only column from bit to integer
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