The site is installed js Fancybox for viewing images. Everywhere works, except for one group of pages. What could be the reason? It is connected everywhere in the template. I can not understand the reason and even in which direction to look

Closed due to the fact that it was off topic by Nicolas Chabanovsky ♦ 5 Dec '16 at 5:17 .

It seems that this question does not correspond to the subject of the site. Those who voted to close it indicated the following reason:

  • "The question is caused by a problem that is no longer reproduced or typed . Although similar questions may be relevant on this site, solving this question is unlikely to help future visitors. You can usually avoid similar questions by writing and researching a minimum program to reproduce the problem before publishing the question. " - Nicolas Chabanovsky
If the question can be reformulated according to the rules set out in the certificate , edit it .

  • do you have errors in the console? - soledar10
  • No, it does not give any errors. Just on the part of the page shows the image as it should, and on the part just opens in the window without using Fancybox. I apologize for not being able to give more adequate information - Alla
  • Write at least some details. What is the peculiarity of this group of pages, after which it began, whether ajax-loading of content is used in the template, give an example of code in the end, anything, and then there are very few psychics - Vasya Shmarovoz
  • Ajax mode in component template settings is disabled. It is shown on the pages of the catalog and is not shown on the pages of the "Articles". It fell off after the layout a long time ago, but did not immediately notice. I would bring the code, but I do not even know what part of the code to show in order to clarify the situation. - Alla
  • I assume the problem is in the component template. Maybe there is a specific line required for the work of the FB? - Alla

1 answer 1

Thank you all for the responses that stimulate the brain process) I remembered everything that happened with these pages and it turned out that the problem is solved simply! When reversing this component, another class was specified. You just need to find this line in the component template and rename the class