CEON URI and UltimateZenCart Mobile Template Photo compatibility?

While I may partially disagree with the statement that generated this thread, that's something else. The OP stated that they have CEON URI installed and the Ultimate Zen Cart Mobile Template installed, but that now the template is using what I assume is to be a product type of product_mobile (ie, main_page=product_mobile) instead of product_info. The OP further stated that when they go to look at a product, the pictures appear to not be properly mapped, supposedly having incorrect information in the image path name. OP stated they would provide website information upon request for review and comment.

Personally, I am not clear about what was meant by the OPs statement of product_mobile being used, and would appreciate some clarification on that subject/topic. I am also not sure if others that had provided comments as to what they thought the source of the issue was had made contact with the OP, as there was no clarifying information provided from them either.

I agree that the template invokes something that is outside of the base installation of ZC, and that one of the two "plug-ins" needs to be modified, to be able to determine which needs tweaking and how to tweak either based on what is going on. Perhaps others could benefit from this information provided by this thread.

Quote:

---

Originally Posted by mc12345678

While I may partially disagree with the statement that generated this thread, that's something else. The OP stated that they have CEON URI installed and the Ultimate Zen Cart Mobile Template installed, but that now the template is using what I assume is to be a product type of product_mobile (ie, main_page=product_mobile) instead of product_info. The OP further stated that when they go to look at a product, the pictures appear to not be properly mapped, supposedly having incorrect information in the image path name. OP stated they would provide website information upon request for review and comment.

Personally, I am not clear about what was meant by the OPs statement of product_mobile being used, and would appreciate some clarification on that subject/topic. I am also not sure if others that had provided comments as to what they thought the source of the issue was had made contact with the OP, as there was no clarifying information provided from them either.

I agree that the template invokes something that is outside of the base installation of ZC, and that one of the two "plug-ins" needs to be modified, to be able to determine which needs tweaking and how to tweak either based on what is going on. Perhaps others could benefit from this information provided by this thread.

---

and gonna say again the issue is the mobile TEMPLATE.. not Ceon URI, not even getting this template to work WITH Ceon URI.. This is why I respectfully suggested moving the discussion to a NEW thread.. The likely issue is that this template is missing code which causing the images to not display properly in the mobile display.. All of this is being ILLUMINATED (rather than caused by) Ceon URI..

Now I don't say any of this capriciously or even lightly, but based on 4 years working with the Ceon URI module and knowing the work and work ethic of the late Conor Kerr.. He designed Ceon URI in a manner that it just WORKS with ANY properly coded template or module.. and when it doesn't, nearly every time it has been demonstrated that the issue was NOT with Ceon URI, but was either an install issue or an issue with some errant template or module..

Now without seeing any of the code for this mobile template to know how it's constructed, I would say it sounds like a mobile product info page is missing code it needs to display things properly.. and if the OP cannot share any of the offending parts of the template files, then they certainly should go back to the place where they purchased the mobile template and get support.

Quote:

---

Originally Posted by mc12345678

While I may partially disagree with the statement that generated this thread, that's something else. The OP stated that they have CEON URI installed and the Ultimate Zen Cart Mobile Template installed, but that now the template is using what I assume is to be a product type of product_mobile (ie, main_page=product_mobile) instead of product_info. The OP further stated that when they go to look at a product, the pictures appear to not be properly mapped, supposedly having incorrect information in the image path name. OP stated they would provide website information upon request for review and comment.

Personally, I am not clear about what was meant by the OPs statement of product_mobile being used, and would appreciate some clarification on that subject/topic. I am also not sure if others that had provided comments as to what they thought the source of the issue was had made contact with the OP, as there was no clarifying information provided from them either.

I agree that the template invokes something that is outside of the base installation of ZC, and that one of the two "plug-ins" needs to be modified, to be able to determine which needs tweaking and how to tweak either based on what is going on. Perhaps others could benefit from this information provided by this thread.

---

Received a comment associated with this that the template is definitely the issue as the template has not been successfully integrated with CEON URI on a test installation. From initial review or perhaps by assumption only the template appears to not be coded using default ZC functions. This would lead one to discover the (potential) short-comings of the template rather than some "problem" with CEON URI.

So, we basically wrote the same thing at nearly the same time, the intent was to ensure applicable information to this conversation stay/join the other parts. I have no need to point out the spcific indivudal that made the statement as that generally has little to do with the issue/question. I fully agree with the assessment of the original author's quality of work. I've only spent the last week or so digging into his coding which is simple in implementation, complex in thought, and in a way elegant.

As part of that review I did identify notes that were left either in the code or in the manual, but it related to coding the product types: product_info, document_info, product_free_shipping_info (or similar) and the like. The statement was that additional product types would need to be added to the file(s) if they were used. The function that contained that information is not one that borrows from the rest of ZC, and so if this "template" were throwing a product type identifier (or if I'm using the wrong term if it is causing main_page to equal product_mobile) then CEON URI would need to "know" something about it in order to fully handle/redirect using the info provided. While we both (all?) still await the OPs input, it sounds like everything other than the images works when the URI is entered as provided through CEON URI.

Sorry for the short post initially, it was right at the end of the work day. And breaking this off into a new thread is perfectly fine by me. And while it relates to CEON URI, which is why I posted in the main thread, you're right, 99.99% chance it's a UCZM issue.

Quote:

---

Originally Posted by DivaVocals

Now I don't say any of this capriciously or even lightly, but based on 4 years working with the Ceon URI module and knowing the work and work ethic of the late Conor Kerr.. He designed Ceon URI in a manner that it just WORKS with ANY properly coded template or module.. and when it doesn't, nearly every time it has been demonstrated that the issue was NOT with Ceon URI, but was either an install issue or an issue with some errant template or module..

---

I AGREE. I actually quite enjoyed his responses. In summary: "This is broken! Fix it!" "Do it right. Follow the gorram instructions. It works fine." "No it doesn't." "Yes it does. READ THE INSTRUCTIONS ENTIRELY." "Oh it works....."

I've already tried adding the mobile page definitions to the product mapping array and it hasn't effected the image issue. We use several additional product types (a feature that I pushed Conor to add in, as there were a couple of hard-coded product type instances that weren't playing nice with our expanded ones), and they work just fine, so now that I think about it more, the product_info vs product_mobile doesn't matter. Upon refresh of a URI'd page, the images all reappear. It's odd, and apparently not an issue that's been encountered yet. I think I will go through all the files that relate to images in both CEON and UZCM and see if I can figure out what in UZCM is causing CEON to break.

Quote:

---

Originally Posted by apogeerockets

Sorry for the short post initially, it was right at the end of the work day. And breaking this off into a new thread is perfectly fine by me. And while it relates to CEON URI, which is why I posted in the main thread, you're right, 99.99% chance it's a UCZM issue.



I AGREE. I actually quite enjoyed his responses. In summary: "This is broken! Fix it!" "Do it right. Follow the gorram instructions. It works fine." "No it doesn't." "Yes it does. READ THE INSTRUCTIONS ENTIRELY." "Oh it works....."

I've already tried adding the mobile page definitions to the product mapping array and it hasn't effected the image issue. We use several additional product types (a feature that I pushed Conor to add in, as there were a couple of hard-coded product type instances that weren't playing nice with our expanded ones), and they work just fine, so now that I think about it more, the product_info vs product_mobile doesn't matter. Upon refresh of a URI'd page, the images all reappear. It's odd, and apparently not an issue that's been encountered yet. I think I will go through all the files that relate to images in both CEON and UZCM and see if I can figure out what in UZCM is causing CEON to break.

---

SO MUCH CLARIFICATION PROVIDED! Thank you for taking the time to flush out more of the details and efforts applied. That is interesting that a refresh resolves the issue. It almost seems that there may be a sequencing issue of the template related to what "data" is available for it at the point it processes the photo info. Obviously a refresh reposts information and with that "new" information it seems that the "normal" "expected" action occurs. Perhaps the image generation of the template is not using standard "up-to-date" methods/calls to generate the link/display the image.

Quote:

---

Originally Posted by apogeerockets

I AGREE. I actually quite enjoyed his responses. In summary: "This is broken! Fix it!" "Do it right. Follow the gorram instructions. It works fine." "No it doesn't." "Yes it does. READ THE INSTRUCTIONS ENTIRELY." "Oh it works....."

I've already tried adding the mobile page definitions to the product mapping array and it hasn't effected the image issue. We use several additional product types (a feature that I pushed Conor to add in, as there were a couple of hard-coded product type instances that weren't playing nice with our expanded ones), and they work just fine, so now that I think about it more, the product_info vs product_mobile doesn't matter. Upon refresh of a URI'd page, the images all reappear. It's odd, and apparently not an issue that's been encountered yet. I think I will go through all the files that relate to images in both CEON and UZCM and see if I can figure out what in UZCM is causing CEON to break.

---

Yep good old Conor!!!:laugh: I do miss him, and what might be construed as arrogance in someone else was pure KNOWLEDGE and confidence coming from the venerable Mr Conor Kerr.. I do believe the issue is in the mobile template code, and the Ceon URI module is simply illuminating the issue.. and I am confident that if Conor were still with us, he would say the same thing.:smile:

If there is a required code change in the mobile template, sharing the answer in the Ceon URI thread would be useful for others who are also using this same mobile template.. I just felt the path to getting to the answer should be worked out in it's own thread..

Quote:

---

Originally Posted by DivaVocals

Yep good old Conor!!!:laugh: I do miss him, and what might be construed as arrogance in someone else was pure KNOWLEDGE and confidence coming from the venerable Mr Conor Kerr.. I do believe the issue is in the mobile template code, and the Ceon URI module is simply illuminating the issue.. and I am confident that if Conor were still with us, he would say the same thing.:smile:

If there is a required code change in the mobile template, sharing the answer in the Ceon URI thread would be useful for others who are also using this same mobile template.. I just felt the path to getting to the answer should be worked out in it's own thread..

---

And I agree that at least the discussion should have spawned off, and wanted to make sure that the applicable discussion was brought into this thread (albeit it got double posted) and didn't want to cause any discontent by doing so. From the little that was originally posted, I didn't want to draw too many incorrect conclusions, with the template being one of the more likely causes. Would think that if the correction is provided in the CeON URI thread, then perhaps this thread be also updated in some way or another once the solution is found.

Quote:

---

Originally Posted by mc12345678

And I agree that at least the discussion should have spawned off, and wanted to make sure that the applicable discussion was brought into this thread (albeit it got double posted) and didn't want to cause any discontent by doing so. From the little that was originally posted, I didn't want to draw too many incorrect conclusions, with the template being one of the more likely causes. Would think that if the correction is provided in the CeON URI thread, then perhaps this thread be also updated in some way or another once the solution is found.

---

I am in fact suggesting that the solution be posted here and a reference (link) to that solution should be shared in the Ceon URI thread.. (which is the usual way folks do this)

So... things.

Example image URL before refresh

HTML Code:

---

<img src="http://beta.apogeerockets.com/Rocket_Kitsimages/thumbs/Cat_RocketSkill1.jpg" alt="Skill Level 1 Kits" title=" Skill Level 1 Kits " width="100" height="100">

---

HTML Code:

---

<img src="http://beta.apogeerockets.com/Rocket_Kitsincludes/templates/apogee_mobile/images/logo-small.png" alt="Mobile Zen Cart" title=" Mobile Zen Cart " width="70" height="40">

---

Example image URL after refresh

HTML Code:

---

<img src="images/thumbs/Cat_RocketSkill1.jpg" alt="Skill Level 1 Kits" title=" Skill Level 1 Kits " width="100" height="100">

---

HTML Code:

---

<img src="includes/templates/apogee_mobile/images/logo-small.png" alt="Mobile Zen Cart" title=" Mobile Zen Cart " width="70" height="40">

---

By adding HTTP_SERVER. before all the DIR_WS_IMAGES calls in the mobile template files, I was able to fix the files in the images folder, but not ones that are located in the template folders. By adding a / before "images" in the definition for the DIR_WS_IMAGES i fix it for the generated images, but not ones that i add in to descriptions and it kills it on the standard site.

It's taken me a while to figure out that the disappearing images is illuminated by CEON URI turning on. I had mentioned to the template author that I was having this problem, and he seemed sure that I had a problem with another module and that was the cause. I will speak with him again with this new information and see if he has suggestions.

Quote:

---

Originally Posted by apogeerockets

So... things.

Example image URL before refresh

HTML Code:

---

<img src="http://beta.apogeerockets.com/Rocket_Kitsimages/thumbs/Cat_RocketSkill1.jpg" alt="Skill Level 1 Kits" title=" Skill Level 1 Kits " width="100" height="100">

---

HTML Code:

---

<img src="http://beta.apogeerockets.com/Rocket_Kitsincludes/templates/apogee_mobile/images/logo-small.png" alt="Mobile Zen Cart" title=" Mobile Zen Cart " width="70" height="40">

---

Example image URL after refresh

HTML Code:

---

<img src="images/thumbs/Cat_RocketSkill1.jpg" alt="Skill Level 1 Kits" title=" Skill Level 1 Kits " width="100" height="100">

---

HTML Code:

---

<img src="includes/templates/apogee_mobile/images/logo-small.png" alt="Mobile Zen Cart" title=" Mobile Zen Cart " width="70" height="40">

---

By adding HTTP_SERVER. before all the DIR_WS_IMAGES calls in the mobile template files, I was able to fix the files in the images folder, but not ones that are located in the template folders. By adding a / before "images" in the definition for the DIR_WS_IMAGES i fix it for the generated images, but not ones that i add in to descriptions and it kills it on the standard site.

It's taken me a while to figure out that the disappearing images is illuminated by CEON URI turning on. I had mentioned to the template author that I was having this problem, and he seemed sure that I had a problem with another module and that was the cause. I will speak with him again with this new information and see if he has suggestions.

---

I promise you it's NOT Ceon URI.. The template is not grabbing the images the way other templates do, and that's the issue.. since NO ONE can see the code from your template, I'm afraid we'd all be guessing at a solution (which isn't particularly helpful IMHO).

Quote:

---

Originally Posted by DivaVocals

I am in fact suggesting that the solution be posted here and a reference (link) to that solution should be shared in the Ceon URI thread.. (which is the usual way folks do this)

---

Which is what I thought would be expected, though not how I read the previous statement. In the end, trying to make sure I think the same goal, solution shared where appropriate.

Maybe a silly question... But does your template correctly include the "base" element in the HTML "head"? And does this element always appear before any other resources (such as CSS and JavaScript)?

Also if you are using jQuery Mobile... Make sure you are using the latest version (see this bugfix)...

Quote:

---

Originally Posted by DivaVocals

I promise you it's NOT Ceon URI.. The template is not grabbing the images the way other templates do, and that's the issue.. since NO ONE can see the code from your template, I'm afraid we'd all be guessing at a solution (which isn't particularly helpful IMHO).

---

I know.... and since it's a purchased template, not sure posting the code is allowed. :/ But you can't use the template without the encrypted pages.... Maybe comparing the full calls between my standard template and my mobile template will provide insight.

Quote:

---

Originally Posted by lhungil

Also if you are using jQuery Mobile... Make sure you are using the latest version (see this bugfix)...

---

Dang, I was hoping the fix would be as easy as that.


Got a timely response from the author!

Quote:

---

I won't be able to help you there. You may contact jsweb. I think they had a fix for it.

You are using two plugins that rewrite URLs. jQuery Mobile rewrites the URLs using Ajax. The only fix I know at least for the jQM portion is to disable Ajax. I don't remember if you may have that option from the admin.

If you disable Ajax, jQM will not rewrite the URLs but you will lose the transition effects.

---

Quote:

---

Originally Posted by apogeerockets

So... things.

Example image URL before refresh

HTML Code:

---

<img src="http://beta.apogeerockets.com/Rocket_Kitsimages/thumbs/Cat_RocketSkill1.jpg" alt="Skill Level 1 Kits" title=" Skill Level 1 Kits " width="100" height="100">

---

HTML Code:

---

<img src="http://beta.apogeerockets.com/Rocket_Kitsincludes/templates/apogee_mobile/images/logo-small.png" alt="Mobile Zen Cart" title=" Mobile Zen Cart " width="70" height="40">

---

Example image URL after refresh

HTML Code:

---

<img src="images/thumbs/Cat_RocketSkill1.jpg" alt="Skill Level 1 Kits" title=" Skill Level 1 Kits " width="100" height="100">

---

HTML Code:

---

<img src="includes/templates/apogee_mobile/images/logo-small.png" alt="Mobile Zen Cart" title=" Mobile Zen Cart " width="70" height="40">

---

By adding HTTP_SERVER. before all the DIR_WS_IMAGES calls in the mobile template files, I was able to fix the files in the images folder, but not ones that are located in the template folders. By adding a / before "images" in the definition for the DIR_WS_IMAGES i fix it for the generated images, but not ones that i add in to descriptions and it kills it on the standard site.

It's taken me a while to figure out that the disappearing images is illuminated by CEON URI turning on. I had mentioned to the template author that I was having this problem, and he seemed sure that I had a problem with another module and that was the cause. I will speak with him again with this new information and see if he has suggestions.

---

Deleted as misunderstood presentation of data/info. Template is trying to push a full path instead of relative path, even though that too is incorrect.

Quote:

---

Originally Posted by apogeerockets

Dang, I was hoping the fix would be as easy as that.


Got a timely response from the author!

---

Quote:

---

I won't be able to help you there. You may contact jsweb. I think they had a fix for it.

You are using two plugins that rewrite URLs. jQuery Mobile rewrites the URLs using Ajax. The only fix I know at least for the jQM portion is to disable Ajax. I don't remember if you may have that option from the admin.

If you disable Ajax, jQM will not rewrite the URLs but you will lose the transition effects.

---

So the issue IS the template which appears to have it's own re-writer built in.. This tells me that this template will probably also be problematic with ANY URL re-writer..

Now one option is that Ceon URI allows you to exclude certain modules from being re-written.. Not sure which file you need to exclude to allow the template's own URL re-writer to do it's thing.. OR the author needs to provide a means to disable it's build in re-writer..

Either way the issue isn't something the URL re-writer needs to correct.. IMHO the TEMPLATE includes conflicting functionality that should have been tested and taken into account by the author..

All that said, and no offense to jsWebs, but they have done NOTHING to support any of the free Ceon modules since taking over Ceon, and I don't expect their assistance here either.. (sorry.. I call things how I see 'em) I am sure that if you utilize their paid support, that they will assist you with a solution. and that is an option you can exercise.. clearly the template author can/will not be able to help either.. so if you want this communities help, you are going to have to share at LEAST the relevant parts of your template code or we will be guessing at things and you will be getting nowhere FAST.. It's open source code whether it's free or commercial and there's NOTHING in the GPL that says you cannot share the code for any reason especially for the purposes of troubleshooting..

Quote:

---

Originally Posted by apogeerockets

...You are using two plugins that rewrite URLs. jQuery Mobile rewrites the URLs using Ajax. The only fix I know at least for the jQM portion is to disable Ajax. I don't remember if you may have that option from the admin. ...

---

One should be able to code their JavaScript to correctly read / use the "base" element when "rewriting" URLs (links should be generated as relative to the "href" attribute of the "base" element when present instead of relative to the current URL).

Barring that, the template should include an option to "selectively" alter the URLs... Or not alter the URLs at all...

On another note, due to the restrictions on calling GPL2 code (such as all of the Zen Cart functions including zen_href_link)... A "commercial" module not released under a compatible license may not be able to fully integrate in Zen Cart (or call these functions)...

Deactivating AJAX ($.mobile.ajaxEnabled=false;) has resolved the problem. Or, rather, eliminated the symptom.

For future reference:

Quote:

---

To remove ajax from the theme do the following:

on your includes/templates/YOUR TEMPLATE _mobile/jquery/jquery_scripts.php

either remove or uncomment lines 23 and 25

23 <?php if (in_array($current_page_base,explode(",",'shopping_cart,checkout_payment')) ) { ?>

and

25 <?php } ?>

Doing so will expose line 24 $.mobile.ajaxEnabled=false; for all pages. That is the line that removes Ajax.

---

I'll still be poking around to see if i can figure out a not-disable-ajax-and-thus-the-animated-transitions solution and post ideas/code snippets/etc here as I go.

Quote:

---

Originally Posted by apogeerockets

Deactivating AJAX ($.mobile.ajaxEnabled=false;) has resolved the problem. Or, rather, eliminated the symptom.

For future reference:


I'll still be poking around to see if i can figure out a not-disable-ajax-and-thus-the-animated-transitions solution and post ideas/code snippets/etc here as I go.

---

Honestly IMHO, the author of the mobile template needs to test their code with the two popular re-writers and correct their code to eliminate conflicts with re-write modules accordingly..

or

you can opt for a responsive template instead which would eliminate these conflicts altogether..

Quote:

---

Originally Posted by DivaVocals

Honestly IMHO, the author of the mobile template needs to test their code with the two popular re-writers and correct their code to eliminate conflicts with re-write modules accordingly..

or

you can opt for a responsive template instead which would eliminate these conflicts altogether..

---

If I may. Perhaps the reason why jsweb has not responded is because they have not been asked. As for the issue between CEON and jQM, I understand that CEON is the best URL rewrite plugin there is. The problem is that jQuery Mobile also rewrites the URL since it uses an AJAX navigation to load the needed content into the DOM. That is why when apogeerockets asked me for a solution, I told her that the only thing she could do was to disable AJAX completely.

Quote:

---

Originally Posted by ultimate_zc

If I may. Perhaps the reason why jsweb has not responded is because they have not been asked.

---

and I don't doubt they have NOT been asked.. **shrugs**