CodePeople2

Hello @bandreas3

Thank you very much for the review.

Best regards.

Hello @emistri

Thank you so much for the review.

Best regards.

Hello @peopleinside

Thank you very much for the feedback. I will release it now.

Best regards.

Hello @peopleinside

Could you please download and install the modified plugin copy by visiting the following link?

https://resources.developers4web.com/cff/tmp/2025/03/05/loading-page.zip

It resolves the issue with the logo image in another way. Its code is the same as version 1.2.3, however, in the logo screen, it includes an onerror event to load a transparent pixel if the logo image is inaccessible.

Please let me know if it works as expected to release this plugin version.

Best regards.

Hello @peopleinside

I’m working on an alternative to the original issue, why we make the modifications from version 1.2.3 to 1.2.4 without modifying the mode that the screen is handled.

Best regards.

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.

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.

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.

Hello @peopleinside

I’m sorry, but on my end both websites (www.peopleinside.it and https://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.

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.

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.

Hello @life2

It depends on how you implemented the form and configured the dependencies. When you reset the form, the plugin must reevaluate all the equations.

The piece of code you included in your entry is incorrect, please rewrite it as follows:

(function(){
if(fieldname1 == 9) {
  ACTIVATEFIELD(fieldname2|n);
  ACTIVATEFIELD(fieldname3|n);
  ACTIVATEFIELD(fieldname4|n);
  IGNOREFIELD(fieldname5|n);
  IGNOREFIELD(fieldname6|n);
  IGNOREFIELD(fieldname7|n);
} else {
  IGNOREFIELD(fieldname2|n);
  IGNOREFIELD(fieldname3|n);
  IGNOREFIELD(fieldname4|n);
  ACTIVATEFIELD(fieldname5|n);
  ACTIVATEFIELD(fieldname6|n);
  ACTIVATEFIELD(fieldname7|n);
}
})()

Best regards.

Hello @life2

Could you please provide the link to the page containing the form to check it in detail?

I’m testing the issues you describe on my end and the reset is working properly. Please watch the following video:

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

Best regards.

Hello @dimytrov

Thank you so much for the review.

Best regards.

Hello @life2

I guess you are referring to the equations’ results. The calculated fields use input tags. The input tags do not support multiline texts. So, the alternative is to use the calculated field to calculate the results, but display them in another control.

Assuming the calculated field is the fieldname123, insert an “HTML Content” field in the form and enter a DIV tag (or any other tag) in its content with the data-cff-field attribute indicating the field whose value you want to display within the tag.

E.g.

<div data-cff-field="fieldname123"></div>

Finally, as the calculated field is used as an auxiliary, you can hide it by ticking a checkbox in its settings.

Best regards.