CMS Made Simple Forums

That's just bizarre, that it would work on 1.11.4, but when you apply the 1.11.5 update it all falls apart.

I am at a loss for ideas.

I will have to install CMSMS 1.11.5 and OSC 2.2 /w STS on my local WAMP stack to find out what's going on. Probably will not get to it until next week sometime.

forgot the actual shopskin link

http://www.rpc.com.au/shopskin/

which is valid xhtml, running 1.11.4

it might be too early to celebrate (i only did some rudimentary testing) but so far i am pleased and relieved to report that the 1.11.6 update appears to fix the problem reported in relation to 1.11.5 update. i assume this bug
http://dev.cmsmadesimple.org/bug/view/9078
was to blame, and change-log indicates it has been addressed.
anyway, shop skin helper looks like it's been restored to former glory. thanks for listening.

Fantastic.

Owens

Could I ask you to look at this thread?

http://forum.cmsmadesimple.org/viewtopi ... =3&t=67874

Do you think the shop_skin_helper has anything to do with this? i doubt it, but am at a loss.

cheers, mario

I checked it out, and the shop skin helper shouldn't have anything to do with those issues. As this script only requires HTML comment tags be added to the CMSMS theme.

stupid me, i posted the wrong link. sorry, here's the correct one if you are interested:

http://forum.cmsmadesimple.org/viewtopi ... =3&t=67873

the stylesheet name was created but not found, and this only happened on the shop pages. the issue is resolved (user error :)

Great! I'm glad you have it resolved.

i've stumbled over a limitation that i'd love to overcome somehow.

Smarty code like does not work. i'm pretty sure cge_is_smartphone is testing the webserver that sends the request for the shopskin, and not the client. any idea how/if I can integrate client testing from shop pages using CMSMS tags/modules?

rotezecke wrote:i've stumbled over a limitation that i'd love to overcome somehow.

Smarty code like

Code: Select all

{cge_is_smartphone assign='is_mobile'}
{if $is_mobile}{set_a_cookie}{/if}

does not work.

The smartphone part is correct.
What part doesn't work for you?
Perhaps for the cookie part this helps: http://www.cmscanbesimple.org/blog/set- ... ug-cookies

Rolf

hi Rolf,
the shopskin helper creates a simple skin ("http://www.rpc.com.au/index.php?page=shopskin") that is split up in three parts and later included by my ecommerce CMS. the three parts are actually written to the server. therefore, i believe, as far as CMSMS is concerned, the client request comes from my own webserver (which i assume is not a smartphone :).
i have some ideas how to work around this issue, but for maintainability, i would have wanted such solutions to be native to CMSMS. looks like this is not possible though.

@rotezecke

You are correct.

The shop skin helper is looking at the final page that is returned to the browser client; all of the CMSMS stuff has fired well before the shop skin helper views the page.

I haven’t tested this exactly. However I have done similar things to get CMSMS content into third party systems.


In a Nut Shell
Create a new template that only has the CMSMS mobile cookie tags in it. Create a page that uses this new template. Have this new CMSMS page called directly by the third party php code that you want to be skinned.


A Rough Explanation
In CMSMS create a template with only the CMSMS cookie stuff. Something like… Then create a page that uses this new template. Uncheck show in menu, and make it not searchable, etc. Give it an alias name like "cmsmsmobilecookiecode" and save it.


In the third party template (where you are including the shop skin files) add some PHP code in the appropriate place to call the CMSMS cookie stuff page. Something like… Let me know how it works out for you.

This works very well. CMSMS template: and the other CMS now includes: Thanks a lot, again.

rotezecke wrote:This works very well.

Glad I could point you towards a possible solution. And thanks for sharing your actual solution. Should help others on their journey.