[Version 1.2.4] Issue on loading screen

Resolved peopleinside
(@peopleinside)

3 weeks, 6 days ago

Hi, I hope you are fine 🌴!
Unfortunately the update from 1.2.3 to 1.2.4 create a big issue to me and I need roll back to 1.2.3 and block the update for now hoping in a fix or solution.

In the plugin settings I have custom CSS code that disable pointer event when the loading screen is showed. This help to avoid user can click on links present on the menu, title article, widget, etc while the loading screen is showed.

With the new update to version 1.2.4 the CSS pointer event none still be present when the loading screen deapear so the website went no more surfable as all menu items and link are no more clickable.

Reverting back to 1.2.3 resolve the issue.

The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 19 total)

1 2 →

Plugin Author CodePeople2
(@codepeople2)

3 weeks, 6 days ago

Hello @peopleinside

I’m sorry for the inconvenience. To fix the issue reported, we released a new plugin update (v1.2.5). Please install the latest plugin update and purge the website and browser caches.

Best regards.

Thread Starter peopleinside
(@peopleinside)

3 weeks, 6 days ago

@codepeople2 thank you for the update!
With this version v1.2.5 simply the custom CSS I insert is ignored during the loading so pointer events that I disabled during the loading is ignored.

Still not working, is a better issue because items are clickable but still broken the functionality I had in all previous version.

Now my custom CSS is simply ignored and I have the issue that user can click on the links while loading are showed.

Maybe I need revert back once again to 1.2.3

Plugin Author CodePeople2
(@codepeople2)

3 weeks, 6 days ago

Hello @peopleinside

Are you sure your website is not loading the files from the cache? Because this update manages the block for Ads or additional code in the same way as version 1.2.3

Best regards.
Thread Starter peopleinside
(@peopleinside)

3 weeks, 6 days ago
Yes I’m sure but let me clean cache again and test again then update here.
Done: result of the test: 1.2.5 still having issue.

You can see I reverted to 1.2.3 on marcoborla.it and all works as expected.

1.2.3 is the last version that works for me.

The issue in peopleinside.it where I’m using 1.2.5 is visible also if you add ?nocache=1 to the URL as you do. Just load that URL, refresh and point the mouse on the menu while the loading screen is showed. The results is that links are clickable when should be not. On marcoborla.it where version 1.2.3 has been restored all works as expected.
- This reply was modified 3 weeks, 6 days ago by peopleinside. Reason: updating the message with more infos
Thread Starter peopleinside
(@peopleinside)

3 weeks, 6 days ago
I don’t know what is different in 1.2.3 that made the extension work while in 1.2.5 is not working as expected. What I can see from the two website source page where I run 1.2.3 and in the another 1.2.5 is a propriety (that I don’t know what is) that looks set different. I don’t know if this is the cause or not.

On 1.2.3
```
"removeInOnLoad":true
```
while on 1.2.5 this is set to false.

I don’t know if this is the cause but I hope in a fix.
If is not a problem I revert also peopleinside.it to 1.2.3 while I hope in a fix that return the functionality of 1.2.3 back.
Plugin Author CodePeople2
(@codepeople2)

3 weeks, 6 days ago
Hello @peopleinside

I’m sorry, but on my end both websites (www.peopleinside.it and http://www.marcoborla.it) are working identically.

I’ll try to describe what I modified in both versions and why.

In version 1.2.3:
```
jQuery('#loading_page_codeBlock,.lp-close-screen').remove();
```
In version 1.2.5
```
jQuery('#loading_page_codeBlock').remove();
jQuery('.lp-close-screen').hide();
```
In version 1.2.3
```
me.attr['overlay'].remove();
```
In version 1.2.5
```
me.attr['overlay'].hide();
```
Version 1.2.3 removes completely ad block, the close screen button, and the loading screen (all tags inside the overlay section).

Version 1.2.5 removes the ad block only (like in version 1.2.3) and hides the other two.

Basically the additional code both manages the ad block at same.

Why we did it?

In version 1.2.3 the plugin creates the DOM for the loading screen each time you need it.

For example, if you configure the plugin to display the loading screen immediately when you click on a link, the plugin generates the loading screen waiting for the browser to navigate to the new page. However, in some situations, like slow networks and no optimized images to include in the loading screen for the website’s logo, the user will see the image space without the image.

Version 1.2.5 hides and shows the loading screen. It does not remove and re-generate the DOM each time you need it. The browser does not need to reload the image, and displays it immediately when you click the links.

Best regards.
Thread Starter peopleinside
(@peopleinside)

3 weeks, 6 days ago

I made a video to show you the issue. It’s not true to me both website works the same, maybe works the same if I revert your plugin version from 1.2.5 to 1.2.3 also on peopleinside.it

See the video of the issue here

Plugin Author CodePeople2
(@codepeople2)

3 weeks, 6 days ago

Hello @peopleinside

Thank you for the video, but I tried to replicate the process. Please look at the result by watching the following video:

https://resources.developers4web.com/cff/tmp/2025/03/05/video_o.mp4

I configured the network to emulate a very slow modem, and while the screen is displayed, the main menu is inaccessible as it should.

Best regards.

Thread Starter peopleinside
(@peopleinside)

3 weeks, 6 days ago

Thank you. I will see maybe it’s just a browser cache issue also if should not as I disable cache in developer console. Seems resolved, I hope. Thank you!
Thread Starter peopleinside
(@peopleinside)

3 weeks, 6 days ago
I have tested more.
Can be an issue still be present on the pre-loading screen?

Watching my video and yours I can see an issue. After updating the plugin the X button to close the preloading is no more big so seems custom CSS is not working.

I feel something still be broken in 1.2.5 but was hard say what. Maybe the issue is still present just in one of the two loading screen? Maybe in the screen showed when a link is clicked?

The X button to close the pre loading is no more big as I customised.
Are you sure there are no CSS issue?

If I revert back the plugin to 1.2.3 I don’t see that issue and I always clean cache from website and browser and I tested with Firefox and Edge so two browsers where I am able to reproduce the issue in 1.2.5 not in 1.2.3

You can see in my previous video the pointer still be the hand and the X button to close the pre-loading is smaller.

This is visible also on your video X is smaller on pre-loading

Rolling back to 1.2.3 resolve the issue. Also I’m unable to reproduce in 1.2.3 the pointer that stay with the symbol of the hand. This happen in my test with 1.2.5 on both browsers on incognito mode while never happen with 1.2.3

Video demonstration with Edge
- This reply was modified 3 weeks, 6 days ago by peopleinside. Reason: new screen gif added no issue on 1.2.3
- This reply was modified 3 weeks, 6 days ago by peopleinside. Reason: added video demonstration
Plugin Author CodePeople2
(@codepeople2)

3 weeks, 6 days ago

Hello @peopleinside

Where you are entering the CSS styles to modify the close button?

If you enter the styles in the “Include an ad, or your own block of code” attribute, this block is removed from the page at the end of the loading process.

What is the difference between version 1.2.3 and 1.2.5? The version 1.2.3 removes the close button as well with the code: jQuery('#loading_page_codeBlock,.lp-close-screen').remove(); So, when you press the link using version 1.2.3, you have no access to the close button, for this reason, you cannot see any difference with the styles. Version 1.2.5 works differently. It hides the close button jQuery('.lp-close-screen').hide(); and displays it again when you click on the links, allowing you to close it. Do you prefer to remove the close button as in version 1.2.3? In my opinion, given access to the user to this button when clicking the link is a better alternative. However, we can consider removing it as in the previous versions, if the majority think that the close button should not be accessible by the users once they click the links to navigate other pages.

Best regards.

Thread Starter peopleinside
(@peopleinside)

3 weeks, 6 days ago

Hum… I discovered now the close button for both version never work anymore for the link screen loading. On peopleinside.it I’m using 1.2.5 and on marcoborla.it 1.2.3 both seems never allow to click the X button that I remember worked in the past.

The differenced I can see between 1.2.3 and 1.2.5 is also the fact using 1.2.5 allow me to click the community menu link and see it opened in a new Windows while with 1.2.3 this was not possible. Seems 1.2.5 block menu links after a while not immediately.

Maybe I have to resign myself as recent updates has maybe changed some things that was working before 😁

Plugin Author CodePeople2
(@codepeople2)

3 weeks, 6 days ago

Hello @peopleinside

The only difference between both versions is that version 1.2.3 removes the loading screen tags and creates them again, while the version 1.2.5 hides the loading screen and shows it.

The behavior you describe with the link happens in both versions of the plugin if you click on the links quickly. This happens because the browser takes some time to trigger the “beforeunload” event.

Please watch the following video. In the first website, I click on the “Info” menu option, and immediately in the “Blog” one, and the website has navigated to the second one. In the second website I click first on “Eventi” and then on “Blog”:

https://resources.developers4web.com/cff/tmp/2025/03/05/video-2_o.mp4

Best regards.
Thread Starter peopleinside
(@peopleinside)

3 weeks, 6 days ago
This is because I restored 1.2.5 also on marcoborla.it I’m testing and see how can I resolve the issue of 1.2.5 now I put back 1.2.3 and the issue is not present.

I’m asking what I can do to avoid links are clickable in version 1.2.5 as my custom CSS inside your plugin seems is not working as on 1.2.3
- This reply was modified 3 weeks, 6 days ago by peopleinside.
Thread Starter peopleinside
(@peopleinside)

3 weeks, 6 days ago

Hum I cannot edit the previous message so I add a detail: another issue of 1.2.5 is that when link is clicked the % is no more showed as 0% but 100%

For now I reverted both my website to 1.2.3 because of the menu link issue that are no more fully disabled by the custom CSS and also the 100% loading percentage showed immediately when a link is clicked. In 1.2.3 when click a link the % showed from 0 not from 100%

Viewing 15 replies - 1 through 15 (of 19 total)

1 2 →

You must be logged in to reply to this topic.