[Resolved] Missing pagination_dots png in views-frontend css file

[Author]

Posts

[larryD-2]

I am trying to:

Fix any errors seen in the Chrome browser console.

Link to a page where the issue can be seen:

hidden link

I expected to see:

No errors.

Instead, I got:

Missing "wp_views/public/image/pagination_dots.png" in "views-frontend.css" file (see image).

P.S. See the second image... How is this a URL in this form's "What is the issue you found?" field?!?

[Mateus Getulio]

Hello Larry,

Thank you for reporting this issue.

I checked it and I can confirm the issue with the missing image.

I'm going to escalate this issue to our developers for a fix and the issue with the ticket titles containing [.] to be wrongly considered URLs to our system teams.

I'd just like your help pointing out how I can replicate the errors in the console/dev tools. I tried reproducing it but so far I wasn't able to. It is going to be useful for me to include it in the escalation.

Thank you, please let me know.
Mateus

[larryD-2]

Hi Mateus,

Well, as far as reproducing the browser console error, it certainly is reproducible on hidden link. And by inspection of the Toolset views-frontend.css file (hidden link) you can see that it includes the line:

background-image:url(../img/pagination_dots.png);

And looking at the wp-views/public/img folder (e.g. in the wp-views download zip file) you can see that there are no images in that folder (just a "shortcodes" sub-folder).

These are all static files in the wp--views plugin. So I believe that's enough information to spot and resolve the problem.

[Mateus Getulio]

Hello Larry,

I escalated this issue to our developers for them to investigate and fix it.

I will set the current ticket status to "Escalated to WPML developers team" and I will get back to you as soon as I get any feedback from them.

Thank you for your patience.

Kind regards,
Mateus

[Mateus Getulio]

Hello Larry,

Thank you for reporting this issue.

Our developers worked on it and corrected the import.

The fix will be available in the next versions of Toolset Views and Toolset Blocks that should be released in the upcoming days.

We have a beta release(sent in the private reply bellow) for both versions in case you want to manually upgrade both plugins to have the issue fixed already.

Thank you,
Mateus