Magento2: Unable to insert multiple catalog product list widgets in CMS page

[kandrejevs]

Preconditions

1. Magento 2.1

Steps to reproduce

1. Insert at least two widgets with type Catalog Product List in CMS page, in my case I want to output 16 products from one category and 16 from another one in homepage (4 products in row with pager and page size- 4)

Actual result

error in CMS page output:

Error filtering template: Element with ID 'widget.products.list.pager' already exists.
and no content at all.

Expected result

Content is displayed properly, error message is absent.

[pboisvert]

@tkacheva can you review if this is a bug or an improvement?

[palamar]

@kandrejevs
Please, provide the used version. If the problem is actual for a specific tag, please, specify it and be sure that the latest update was used.

[tkacheva]

@palamar I had the same issue - MAGETWO-54911 please check

[Thuan1234]

Yes, The problem is still there. We have same issue now (version 2.1.1). I have also checked the problem on Magento Sample Data package (V2.1.1) . But we can solve this problem by disabling all cache types from Cache Management. However, the site could take 15- 20 second to load.
Anyway, its big bug. Please fix it soon
Thanks

[phuongnd]

@tkacheva do you know when this is fixed?

[ooples]

I'm getting this error as well

[ksilliman-pipeline]

I'm getting this error too. (version 2.1.1)

[joshspivey]

Issue is still on 2.1.3 also. But just setting the option to remove pagination seems to work until you have the issue resolved.

[KingKarrow]

Issue still in 2.1.3. Does anyone have a workaround?

[caliboy007]

Issue is still in 2.1.5, possible due to pager (pagination) and page_var_name which seems to be generated unique to each category product list widget generated.

What worked for me was under 'Category Products List' select Display Page Control to 'No'.

Hope this helps! Permanent solution still needed.

[phuongnd]

Yep this issue is still in Magento 2.1.5. You can temporary solve it by Disable Blocks HTML output cache

[smokygeek17]

Bug is still present in 2.1.6

[smokygeek17]

@phuongnd disabling the block output doesn't help :(

[johnsonmasih]

There error in 2.1.7 too, couldn't find the solution on whole internet...

[phuongnd]

@smokygeek17 do you refresh the cache?

@johnsonmasih just disable blocks HTML output cache, it will be sorted out.

[johnsonmasih]

@phuongnd Refreshing cache or disabling blocks HTML output cache didn't work

[phuongnd]

@johnsonmasih we're using multi widget here http://novetty.zooextension.com/stores/store/switch/?___store=home9_en and it's working very well.

[smokygeek17]

@phuongnd Yes it did. And your next advise to disable the HTML output cache didn't work.

We just used the "SKU is one of" option and listed all SKUs that are needed.

But it's obviously a bug.

[phuongnd]

@smokygeek17 yes, it's exactly a bug. Disable block html cache is just a temporary solution.

[atsareva]

Hi guys! Any updates here? Thanks

[magento-engcom-team]

@kandrejevs, thank you for your report.
We've created internal ticket(s) MAGETWO-54911 to track progress on the issue.

[guleym]

Bug present in 2.1.9

[alexanderlukjanenko]

Hi any update on this issue?
I have the same error on Magento 2.1.10
When add show_pager="1" attribute.

[mfsi-subhras]

Hey, I faced the issue in Magento 2.2 as well. Can you please let know the solution of the same.

[pixiemediaweb]

we had this issue too. Quick solution is duplicate the widget phtml file, so you never have the same template loaded twice on the same page.

[anilspurtree]

This issue is still present in 2.2.6 version any updates ??

[anilspurtree]

The only solution seems to be disable pagination "Display Page Control" to NO

[vasilii-b]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @vasilii-b. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @vasilii-b, here is your Magento instance.
Admin access: http://ec2-34-228-235-121.compute-1.amazonaws.com/i-4468-2-3-develop//admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

Hi @vasilii-b. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

• [x] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [x] 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
  

• [x] 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• [ ] 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[vasilii-b]

@magento-engcom-team give me 2.2-develop instance

[magento-engcom-team]

Hi @vasilii-b. Thank you for your request. I'm working on Magento 2.2-develop instance for you

[magento-engcom-team]

Hi @vasilii-b, here is your Magento instance.
Admin access: http://ec2-34-228-235-121.compute-1.amazonaws.com/i-4468-2-2-develop//admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[sidolov]

Hi @kandrejevs. Thank you for your report.
The issue has been fixed in magento/magento2#18714 by @vasilii-b in 2.3-develop branch
Related commit(s):

• 0a253644a43f39d8ab40701011512534f4fc34bb

The fix will be available with the upcoming 2.3.1 release.

[magento-engcom-team]

Hi @kandrejevs. Thank you for your report.
The issue has been fixed in magento/magento2#18874 by @gelanivishal in 2.2-develop branch
Related commit(s):

• 3f17772611af437165443aa2d4ac9c3a27945225

The fix will be available with the upcoming 2.2.8 release.

[phumlaninyati]

I am on magento 2.3.0 this issue is still not fixed.