Return to previous page

Errors in recent XStore Core plugin causes issues with Customizer & other plugin

This topic has 21 replies, 3 voices, and was last updated 5 years, 9 months ago ago by Rose Tyler

Robert

Participant

February 18, 2020 at 03:46

Hello

On one of my XStore sites, I have installed a popular news feed plugin called Epics News Elements.

https://codecanyon.net/item/epic-news-elements-news-magazine-blog-element-for-elementor-wpbakery-page-builder/22369850

I didn’t update XStore for many months on this site from way back to v5.x. I recently updated to the latest XStore and Core, but now the site hangs while loading the customizer. When Xstore Core plugin is deactivated, the customizer loads as it should.

The author of Epics News Elements found errors in the console coming from the XStore Core Plugin.

https://prnt.sc/r3trs0

These are Javascript errors that specifically come from the core plugin, not elsewhere and are the reason why the customizer hangs only when it runs both together with Epics News Elements plugin. If either is disabled then the customizer works, but since the Javascript errors come from the core plugin, it must be the core plugin causing the issue.

Please, investigate?

Regards
Robert

#229912 Copied Theme version: 6.2.10

20 Answers

John Holden

Participant

February 18, 2020 at 05:16

Hi,

Please send:

– FTP info (server, username, password, port)
– Admin info (wp-admin URL, username, password)

I will check this problem for you.

Regards,
Hung PD

#229916 Copied

Robert

Participant

February 18, 2020 at 06:02

Hello Hung The

Please see private area for credentials.

I have enabled the Under Construction plugin, so head straight to the login URL I included and copy and paste that. I suggest first seeing what happens when you open the customizer. It will hang with all plugins enabled. Disabling either the XStore Core or Epics News Elements plugin will allow the customiser to work. The JS errors come from the core though.

NB – Please do not post details of the site url in the public area. also post any screenshot links in private area too, thanks.

Robert

Please contact administrator
for this information.

#229917 Copied

Rose Tyler

Support staff

February 19, 2020 at 08:27

Hello,

We can’t log in to your site, there is a blank screen by URL you provided. Please check.

Regards

#229939 Copied

Robert

Participant

February 19, 2020 at 19:11

Hi Rose

Very sorry, please try this one in private area.

Robert

Please contact administrator
for this information.

#229976 Copied

Robert

Participant

February 19, 2020 at 22:59

Please note, I have updated XStore to 6.2.11 and Core to 2.2.1, but still have a problem with customizer hanging.

#229979 Copied

John Holden

Participant

February 20, 2020 at 05:44

Hi,

– I can’t enable debug because of permission denied
– You changed xstore directory, please re-upload original theme, then try again

Regards,
Hung PD

Please contact administrator
for this information.

#229988 Copied

Robert

Participant

February 20, 2020 at 07:23

Hung The

Please read private message

I asked you this already before…

NB – Please do not post details of the site URL in the public area. also post any screenshot links in private area too, thanks.

With regards to file permissions, you can manually change the permissions to writeable using any FTP program. For example, FileZilla, you can right-click the file and set the permissions there from 444 to 644. This is standard practice using an FTP client application.

Please contact administrator
for this information.

#229989 Copied

Robert

Participant

February 20, 2020 at 07:30

Along time ago, when I purchased XStore, I spoke with your colleagues in support and they said it was OK to change the folder name from xstore to what I wanted, by altering style.css. I use many different themes on behalf of clients, and it’s quite normal for web designers to use themes as base templates and change the theme folder name to hide the fact that a template has been used. It’s normal in the industry.
I have had no problem over the years I’ve used XStore up until recent updates. If the theme folder is the problem, then I can no longer buy XStore. I have over 8 licenses in my name and many others I had clients purchase. If I am forced to rename the folder name back to xstore for the site to function, then its the last one that I will be buying, and for this site, I will switch to another theme. It’s easy for me to replicate the look of the site with another theme.
I request that in a future update, you do not code your Core plugin that specifies the folder name as xstore. This problem is new due to updates you’ve made.

#229990 Copied

Robert

Participant

February 20, 2020 at 09:06

If recent updates to the XStore Core plugin are causing the problem, as I suspect, and you think its related to a folder name being changed for the theme, then please see the following link for your theme author to code the Core plugin so it finds the current theme URL and you do not hard-code the word “xstore” into the URL of the javascript you are calling.

https://developer.wordpress.org/reference/functions/get_template_directory/

and

https://paulund.co.uk/get-theme-directory-in-wordpress

Robert

#229995 Copied

Rose Tyler

Support staff

February 20, 2020 at 10:54

Hello,

Problem caused by Epic News Elements plugin, there are js errors if plugin is enabled http://prntscr.com/r51w23 Once we disable plugin everything works fine http://prntscr.com/r51uox So, contact plugin author to find out why it causes js errors.

Regards

#229997 Copied

Robert

Participant

February 20, 2020 at 11:57

Hi Rose

Thanks.

I have passed on your message to the Epic News Theme author. However, he has already stated that it’s your Core plugin causing the JS errors and the customizer also works when Core is disabled. I will wait until Epic News author responds following your screenshots.

Robert

#229999 Copied

Robert

Participant

February 21, 2020 at 19:58

I’m getting nowhere with the Epic News plugin author. This is his reponse to the screenshots you provided:-

About the Customizer issue, It seems it related to compatibility issues, our plugin works fine with the standard WordPress Customizer. So it will need some adjustment to the code but this is not our support scope, you can check our support policy, I hope you don’t mind. Let us know if you have further questions.

Thank you

Not sure about my next move now. Will have a think and see if there is an alternative plugin to display news on a site.

Robert

#230113 Copied

Robert

Participant

February 22, 2020 at 05:51

Hi again Rose

I am sorry, but I have done further investigation myself from the Google Chrome console.

Please see this screenshot: https://prnt.sc/r5zt4e

In the list of Javascript errors, when I hover over them, most of them relate to javascript from your core plugin, as the author of Epic News had told me.

https://theatrelife.co.uk/wpcontent/plugins/et-core-plugin/packages/kirki/controls/js/script.min.js

I strongly do not believe that the Epic News plugin is at fault here. The Javascript faults are directly connected to your Xstore Core plugin as was previously mentioned, and the URL of the Javascript indicates exactly where the errors are to be found.

Will you now pass this onto the developer to look at and provide a solution?

Robert

#230120 Copied

Rose Tyler

Support staff

February 23, 2020 at 09:26

Hello,

I have sent this problem to our technicians, they will be able to take a look from Monday.

Regards

#230152 Copied

Robert

Participant

February 23, 2020 at 12:47

Thank you.

#230160 Copied

Rose Tyler

Support staff

February 24, 2020 at 12:39

Hello,

Our theme uses Kirki framework that has repeater control https://kirki.org/docs/controls/repeater , the Epic News plugin uses similar control for own purposes too, but Epic News plugin added in each its controls prefix ‘jeg-‘ but not for repeater control.
We have renamed http://prntscr.com/r6uyr3 to http://prntscr.com/r6uz00 (epic-news-element/lib/jeg-framework/customizer/control) , and the Customizer works fine now.
We would recommed you to contact authors of the plugin and ask to rename this control because other their controls were named like this – https://gyazo.com/731dab6d03a48d3f2628151de3893df6

Regards

#230200 Copied

Robert

Participant

February 25, 2020 at 10:57

Hi Rose ?

Many thanks to you and your team for going to the trouble of finding the culprit. I know this goes beyond your usual remit of support, so I am eternally grateful for this.

I got an email today from the author of Epic News Elements providing the exact same fix you did a day after you found it, with the exact same replacement of the variable to jeg-repeater. Maybe a coincidence, but I did provide them with a link to this thread some while back. Who knows.

It is difficult when this type of conflict arises from the naming of a variable, but thanks to your perseverance in this case.

Robert 🙂

#230244 Copied

Rose Tyler

Support staff

February 25, 2020 at 12:07

Hello,

Yes, that was a third-party plugin but our developers dug up faster in it than the developers of the plugin. We have lost a bit of our own time for that, so would you mind to rate our product: https://prnt.sc/d256m6 https://themeforest.net/downloads 🙂 That would be much appreciated.

Regards

#230250 Copied

Robert

Participant

February 25, 2020 at 13:25

Rose

https://prnt.sc/r7e0k8

Maybe I said too much ?. Too many competitors will want your theme now. ?

Robert

#230274 Copied

Rose Tyler

Support staff

February 25, 2020 at 13:54

Hello,

Thank you very much!!! 🙂

Regards

#230282 Copied
Viewing 21 results - 1 through 21 (of 21 total)

The issue related to '‘Errors in recent XStore Core plugin causes issues with Customizer & other plugin’' has been successfully resolved, and the topic is now closed for further responses

Errors in recent XStore Core plugin causes issues with Customizer & other plugin

Explore our best WordPress WooCommerce Themes collection