Questionable url "np://" in body tag

v.piasta
31 Posts
v.piasta posted this 24 June 2023
Ask a Question

Among the elements in the body tag of my pages, I find this definition:
data-bg="url("np://user.desktop.nicepage.com/Site_#########/images/20211211_091643-2-1080.webp?rand=824a")"

I imagine np://stands for "nicepge.com" in some way but I presume a browser would not recognize it as such as it is non-standard.
Why is this pointing to nicepage.com instead of a file on my server, and what is the effect?
My web pages should all be independent of the nicepage.com server once they have been created.
Could the presence be due to a compilation error? How do I eliminate this element and what happens if I do?

Among the elements in the body tag of my pages, I find this definition: data-bg="url("np://user.desktop.nicepage.com/Site_#########/images/20211211_091643-2-1080.webp?rand=824a")" I imagine np://stands for "nicepge.com" in some way but I presume a browser would not recognize it as such as it is non-standard. Why is this pointing to nicepage.com instead of a file on my server, and what is the effect? My web pages should all be independent of the nicepage.com server once they have been created. Could the presence be due to a compilation error? How do I eliminate this element and what happens if I do?
Vote to pay developers attention to this features or issue.
4 Replies
Order By: Standard | Newest
Support Team
Support Team posted this 26 June 2023

Hello Volker,

The presence of the data-bg attribute with a value pointing to np://user.desktop.nicepage.com indicates that the background image URL is being fetched from the Nicepage server instead of being hosted on your own server. This behavior is typically expected when using the Nicepage website builder or editor to create and manage your web pages.

When you create a website using Nicepage, the editor may reference resources such as images, stylesheets, or scripts from the Nicepage server. This approach allows Nicepage to provide convenient access to these resources and ensures that your web pages are displayed correctly within the editor environment.

...................................................
Sincerely,
George.
Nicepage Support Team

Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1
Follow us on Facebook: http://facebook.com/nicepageapp

Hello Volker, The presence of the data-bg attribute with a value pointing to np://user.desktop.nicepage.com indicates that the background image URL is being fetched from the Nicepage server instead of being hosted on your own server. This behavior is typically expected when using the Nicepage website builder or editor to create and manage your web pages. When you create a website using Nicepage, the editor may reference resources such as images, stylesheets, or scripts from the Nicepage server. This approach allows Nicepage to provide convenient access to these resources and ensures that your web pages are displayed correctly within the editor environment. ................................................... Sincerely, George. Nicepage Support Team Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1 Follow us on Facebook: http://facebook.com/nicepageapp
v.piasta
31 Posts
v.piasta posted this 27 June 2023

Thank you for the explanation, this is what I suspected. Can this behavior be switched off? I have subscribed to the Nicepage editor because, opposite to other editors, it was supposed to create webpages that are not depending on the Nicepage server. The characteristic undermines the website's independence.
Most of the resources are correctly obtained from our own server, We don't want any of our resources to be stored on Nicepage's servers.
On this occasion, I would also like to understand the need for elements like "data-lang-fr=" (French text) " in any other language version of an HTML file other than the French version. The same happens for all other languages that are used, they contain the text of other languages which in my view is useless clutter that only increases the size of the file and thus its load time. Why is this not eliminated during compilation? Does it have any practical use?

Thank you for the explanation, this is what I suspected. Can this behavior be switched off? I have subscribed to the Nicepage editor because, opposite to other editors, it was supposed to create webpages that are not depending on the Nicepage server. The characteristic undermines the website's independence. Most of the resources are correctly obtained from our own server, We don't want any of our resources to be stored on Nicepage's servers. On this occasion, I would also like to understand the need for elements like "data-lang-fr=" (French text) " in any other language version of an HTML file other than the French version. The same happens for all other languages that are used, they contain the text of other languages which in my view is useless clutter that only increases the size of the file and thus its load time. Why is this not eliminated during compilation? Does it have any practical use?

Last edited 27 June 2023 by v.piasta

Support Team
Support Team posted this 30 June 2023

Hello Volker,

Thanks for the reply

Regarding the behavior of fetching resources from the Nicepage server, I understand your concern about the independence of your website. Currently, Nicepage relies on its server to serve certain resources to ensure the smooth functioning of the editor and consistent display of the web pages during the editing process. However, when you publish your website, Nicepage is designed to export all necessary files, including images, stylesheets, and scripts, so that your website can be hosted independently on your server or hosting provider. This means that when you publish your website, it's no longer dependent on the Nicepage server.

Regarding the "data-lang" attributes, they are used to define language codes for multi-language support in web pages. Nicepage includes these attributes to facilitate the creation of multi-language websites. These attributes allow you to define different versions of the content in multiple languages within the same HTML file, making it easier to manage and maintain multilingual websites.

While these attributes may increase the file size to some extent, they serve a practical purpose in facilitating multi-language support and enabling search engines to understand the different language versions of your web pages. However, suppose you're not utilizing the multi-language functionality or find it unnecessary for your website. In that case, you can manually remove or clean up the unused language attributes to reduce the file size. Please note that we do not recommend removing the code to avoid unstable functioning of the website

I hope this clarifies the behavior and purpose of these elements in Nicepage. If you have any further questions or concerns, please let me know.
...................................................
Sincerely,
Ahmad.
Nicepage Support Team

Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1
Follow us on Facebook: http://facebook.com/nicepageapp

Hello Volker, Thanks for the reply Regarding the behavior of fetching resources from the Nicepage server, I understand your concern about the independence of your website. Currently, Nicepage relies on its server to serve certain resources to ensure the smooth functioning of the editor and consistent display of the web pages during the editing process. However, when you publish your website, Nicepage is designed to export all necessary files, including images, stylesheets, and scripts, so that your website can be hosted independently on your server or hosting provider. This means that when you publish your website, it's no longer dependent on the Nicepage server. Regarding the "data-lang" attributes, they are used to define language codes for multi-language support in web pages. Nicepage includes these attributes to facilitate the creation of multi-language websites. These attributes allow you to define different versions of the content in multiple languages within the same HTML file, making it easier to manage and maintain multilingual websites. While these attributes may increase the file size to some extent, they serve a practical purpose in facilitating multi-language support and enabling search engines to understand the different language versions of your web pages. However, suppose you're not utilizing the multi-language functionality or find it unnecessary for your website. In that case, you can manually remove or clean up the unused language attributes to reduce the file size. Please note that we do not recommend removing the code to avoid unstable functioning of the website I hope this clarifies the behavior and purpose of these elements in Nicepage. If you have any further questions or concerns, please let me know. ................................................... Sincerely, Ahmad. Nicepage Support Team Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1 Follow us on Facebook: http://facebook.com/nicepageapp
v.piasta
31 Posts
v.piasta posted this 02 July 2023

Ahmad, I am using multi-language pages. But when they are exported, they are automatically sent to a subdirectory for each language. An HTML file exported to the /en subdirectory is expected to be in English, so all other data-lang elements like "fr", "de" or "it" serves no purpose there. The browser does not need them at all. This looks just like useless clutter that the Nicepage engineers have forgotten to clean up. The same is true for the reference to the website server. It is extra work for the user to eliminate these useless things, and they have to be eliminated every time I update something on any page because the exportation is always made for ALL pages. This is not what I bought into.
Instead of adding features of little importance, Nicepage should fix the existing problems. Extreme cluttering of the exported files is one of them because it makes the optimization of the load time impossible. The fact that there are references to the nicepage server that we, the users, would have to edit manually each time any page is updated, is unacceptable. This must be done DURING the exportation process, and the exported files must be clean.
I am absolutely not satisfied with the quality of Nicepage and I am considering alternatives before my subscription term expires.
I had hoped to keep this subscription for the future, but it seems very improbable now.
I hope this feedback reaches some of the responsible people, and not only you people on the support that won't change any of the things that don't work.

Ahmad, I am using multi-language pages. But when they are exported, they are automatically sent to a subdirectory for each language. An HTML file exported to the /en subdirectory is expected to be in English, so all other data-lang elements like "fr", "de" or "it" serves no purpose there. The browser does not need them at all. This looks just like useless clutter that the Nicepage engineers have forgotten to clean up. The same is true for the reference to the website server. It is extra work for the user to eliminate these useless things, and they have to be eliminated every time I update something on any page because the exportation is always made for ALL pages. This is not what I bought into. Instead of adding features of little importance, Nicepage should fix the existing problems. Extreme cluttering of the exported files is one of them because it makes the optimization of the load time impossible. The fact that there are references to the nicepage server that we, the users, would have to edit manually each time any page is updated, is unacceptable. This must be done DURING the exportation process, and the exported files must be clean. I am absolutely not satisfied with the quality of Nicepage and I am considering alternatives before my subscription term expires. I had hoped to keep this subscription for the future, but it seems very improbable now. I hope this feedback reaches some of the responsible people, and not only you people on the support that won't change any of the things that don't work.

Last edited 02 July 2023 by v.piasta

You must log in or register to leave comments