• Priority: High
  • Status: Closed
  • Theme: Alysum
  • Assigned To: Marek
  • Private: No
  • Open Date: 04.01.19, 20:39
  • Opened by: Matata Neso
  • Closed by: Marek
  • Closed on: 01.02.19, 12:25
  • Reason: No answer from a customer

Ticket #13470 - AMP Theme, Products not showing when selected from menu

When opening the menu and selecting any of the categories, None of the products is showing

while working fine on the WEB

Only the widget of the products is working on the home page


Marek 05 Jan 2019, 11:28

You have to enable “https” to use AMP version.

Matata Neso 06 Jan 2019, 17:50

SSL Enabled and Installed and Still Cant see the Products, Can you please check

Marek 07 Jan 2019, 11:32
Matata Neso 08 Jan 2019, 19:57

I have Check all, and done

Still i didn’t get the last check
Make sure permissions of the module folder and files are correct.

From where can i check this otherwise all is Done

Marek 09 Jan 2019, 10:41

Sorry, but I’m no able to connect to your server, here is an error messages of my FTP client

Status:      	Resolving address of ftp.bride2be.ae
Status:      	Connection attempt failed with "EAI_NONAME - Neither nodename nor servname provided, or not known".
Error:        	Could not connect to server
Matata Neso 09 Jan 2019, 15:43

FTP Host :

USER : [email protected]
Password : [email protected]

I just Connected on the same

Marek 10 Jan 2019, 01:41

There is some restrictions in your server configuration what blocks requests to AMP files. How can I take a look at apache error logs to figure our what is the reason exactly?

Matata Neso 11 Jan 2019, 03:54

Can you advise which access you need and i will provide please

Matata Neso 11 Jan 2019, 04:06

I guess I got the error while checking i found the below

Mixed Content: The page at ‘https://bridees.ae/psnew/module/pk_amp/category?id_category=23’ was loaded over HTTPS, but requested an insecure favicon ‘http://www.bride2be.ae/‘. This request has been blocked; the content must be served over HTTPS.

Can i do anything about this one

Marek 11 Jan 2019, 10:53

I see that, but I suppose that is not a major issue. The best way to figure that out is to take a look at apache error logs. You have to ask your hosting support to help you to get those logs