Do stuff on product id

I am trying to generate HTML for something in the head section on product information pages only.

So what would be the correct way to write something like this?

if ($current_page_base == 'index' and $cPath == '1' and $products_id == '123') {
  echo 'DO STUFF';
}

I've tried a few different variations, no success though. Thought something like this might work.

if ($current_page_base == 'product_info' and $products_id == '123') {  echo 'DO STUFF';} 

what I am trying to is output an AMP Page URL for product information pages. I can do this on categories by doing this.

if ($current_page_base == 'index' and $cPath == 'YOUR_CATEGORY_ID') {  echo '<link rel="amphtml" type="text/css" href="https://yoururl.com/your-category-name-or-url">';}

But can't see how I would do similar for a product information page. I need to be able to specify the exact product information page id in a similar way to $cPath == 'YOUR_CATEGORY_ID'

I suspect $products_id is not set at the point you are injecting your code. Try using $_GET['products_id'].

And if your product has attributes, would recommend casting the $_GET['products_id'] to an integer otherwise when clicking on a product link in the shopping cart the "message" will not be displayed.

ok this worked

if ($current_page_base == 'product_info' and $_GET['products_id'] == '123') {  echo '<link rel="amphtml" type="text/css" href="https://MYDOMAINNAME.com/my-url-1.html">';} 
if ($current_page_base == 'product_info' and $_GET['products_id'] == '234') {  echo '<link rel="amphtml" type="text/css" href="https://MYDOMAINNAME.com/my-url-2.html">';}

You would keep repeating the entries in tpl_main_page.php and where it reads $_GET['products_id'] == '234') - enter your product id.

<link rel="amphtml" type="text/css" href="https://MYDOMAINNAME.com/my-url-2.html">
``` - would be the link to your AMP page


Thanks for the help guys, if you have anything else to add to this please let me know

To make your page(s) more flexible for relocation, would suggest that the destination links be made more generic so that one doesn't have to update the domain name or the connection method. If the page is located in the root of the catalog then need only to have the href="my-url-2.html" as an example.
If it is at the root of the domain (where the catalog is found in a sub-folder), then thought should be able to use href="/my-url-2.html".

mc12345678:

To make your page(s) more flexible for relocation, would suggest that the destination links be made more generic so that one doesn't have to update the domain name or the connection method. If the page is located in the root of the catalog then need only to have the href="my-url-2.html" as an example.
If it is at the root of the domain (where the catalog is found in a sub-folder), then thought should be able to use href="/my-url-2.html".

OK yes I get your point and thanks for that. I will look into it. There are some pages that can't go in the root as there are already lightweight HTML landing pages with similar names. But I think the product pages could go there.

Excellent info on relative links at https://www.w3schools.com/html/html_filepaths.asp

dbltoe:

Excellent info on relative links at https://www.w3schools.com/html/html_filepaths.asp

Yeah I know all that but I am just not sure if it works the same for AMP pages as they appear to recommend the full URL including the domain name. I suppose the only way to find out though is try it.

Starting in 2016 and continuing through 2018, they say use https://... At least that won't cause the mixed content warning on a site.

dbltoe:

Starting in 2016 and continuing through 2018, they say use https://... At least that won't cause the mixed content warning on a site.

Thats what i thought i had read. I've been working on structured data this evening though so not had a chance to look again. Structured data is definitely not as easy as it seems and i find googles validation tools can be buggy. Anyway different subject for another time.

Yeh, didn't want to muddle the puddle too much. More recent at http://aqualab.cs.northwestern.edu/wp-content/uploads/2019/02/AMP-Mobicom-2019.pdf but, it talks about four different URLs at the top of page 3.
:huh:

dbltoe:

Yeh, didn't want to muddle the puddle too much. More recent at http://aqualab.cs.northwestern.edu/wp-content/uploads/2019/02/AMP-Mobicom-2019.pdf but, it talks about four different URLs at the top of page 3.
:huh:

Well as far as I know, only two URL's corresponding to the same page or content can exist in google. The other two URL's are referring to the AMP Cache and AMP Viewer. So one None AMP page will exist in the search for Desktop Users or Laptop Users, and the AMP Page will exist in the search on a mobile phone or tablet. However the advantage is the speed of the website in Google terms.

I've worked alot on AMP, Structured Data, and implementing .webp images in Zen Cart these last few weeks. AMP and .webp give a massive advantage on speed and structured data feeds google all the data it requires quicker than reading the whole web page (although it will obviously still crawl it). Add them all together and there are some massive advantages to be had with page rank. But none of them are easy to implement and take a bit of time and patience to say the least. However, if you want to stay ahead then obviously you have take these new technologies on board.

My comment to those that don't want to look at the new is, "Clinging tenaciously to the trailing edge of technology.":P

dbltoe:

My comment to those that don't want to look at the new is, "Clinging tenaciously to the trailing edge of technology.":P

hahaha...yes and end up stuck in a cloud of smog trying desperately to see daylight :D....and then when they do, this happens :jawdrop: