Hi , very often WordPress automatic check advise me about this error in object when I make some plugins updates. As the cause it mentions xstore core! Can you solve this please? Thanks a lot
This topic has 8 replies, 3 voices, and was last updated 11 months, 1 weeks ago ago by Andrew Mitchell
Hi , very often WordPress automatic check advise me about this error in object when I make some plugins updates. As the cause it mentions xstore core! Can you solve this please? Thanks a lot
Hello @gabrielet,
This error might occur if any modifications were made to the Core plugin on your end. However, since no screenshots or videos of the issue were provided, we are unable to fully understand the exact problem that arose during the update.
If you have any additional details, such as screenshots or a video, please share them with us so that we can investigate the matter more thoroughly.
Best regards,
Jack Richardson
The 8Theme Team
answer on the private content area. check it out
Hello, gabrielet,
Thank you for reaching out to us.
Could you please provide updated access credentials for the admin panel and FTP? Unfortunately, the credentials you previously shared are no longer working. Additionally, we kindly ask you to share the correct link to access the admin panel, as the default links appear to be blocked.
We appreciate your assistance and look forward to your response.
Best regards,
8Theme Team
Please read the Answer on the Private area, thanks a lot
Hello, gabrielet,
Thank you for providing access. We have addressed and resolved the issue. Kindly verify the changes, which have been made in the following file:
et-core-plugin/app/models/overview/template-parts/html-overview.php
Additionally, please note that these changes will be included in the next theme update.
Best regards,
8Theme Team
Ohhh, well finally a good news, we will check, thanks a lot by now, We hope it solved, bye
Thank you for your cooperation and we look forward to hearing from you soon.
The issue related to '‘WordPress E_Error type error line 109. Missing format specifier’' has been successfully resolved, and the topic is now closed for further responses