• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Problems in Eshop

I

ikelg

Guest
Hello,

When I access a category with more than 30 photos in eshop, and try to move to the next page to view the next product, instead of, go to the next page, eshop back to the homepage of the categories.

Can you help me please?
 
Does this issue appear on published site? Could you please provide the example of such a site?
By the way, you could try to update to latest 4.5 version and check this case there.
 
As I can see there is some error message exists on E-shop page:

"Incapaz de executar a query no banco de dados SQLite." So it looks like there is something wrong with modules database or something. Could you try to re-publish the entire site and check it one more time? Also, check for details errors in Parallels Plesk Sitebuilder admin CP -> Logs section if there any issues with publication. Most probably this is related to issue with paging.
 
someone have a solution? Or I really have to do the upgrade to 4.5?

Thanks.
 
I have consulted with developers and there are two ways to resolve this case:

1. Upgrade Parallels Plesk Sitebuilder to latest 4.5 release, re-publish the entire site and issue should be automatically resolved. This way is more preferable as some other issue from version 4.2 will be also resolved.
2. Create a support ticket with the reference to this thread so we could pass it to developers for investigation.

Let me know how everything goes.
 
Back
Top