My website isn't updating when I add files to it? - godaddy-api

when i added the files in GoDaddy filemanager.. my website didn't change the content. It shows a GoDaddy content.
enter image description here
how to clear this problem?

If your inspect this HTML page you will not see any trace of your work. Check your configuration, which page is launch while get your URL. How did you deploy your work?

do you upload your published website to your host??
check if index.html or defualt.html or … is exist remove them and use your index website page

Related

Serve files from dcos as .html docusaurus

Problem
Noticing when I upload my 'build' content to the server, the md files in docs are breaking.
Not sure why, but there are clearly '.html' files.
But reloading the page doesn't work and i18n doesn't work either.
What confuses me
So, I tried directly accessing the page with '.html' link.
Just to show you,
http://coding-insight.com/docs/python/start/python/ displays 404 when using direct link.
However, using the site's menu bar works.
Reloading results in 404.
But there are clearly html files in the server.
https://user-images.githubusercontent.com/78584173/179334770-46bb6e02-cf6a-4a76-be40-c3fe71038622.png
So, I tried accessing html files directly.
https://coding-insight.com/docs/python/start/python.html
It works. Reloading works.
Question
So, are there any way I could access the html files directly rather than using those '/' at the end?
Is it a bug?

GitHub pages repository linked to a custom domain, but the content is not rendering

I've deployed my web site to GitHub pages and it worked perfectly with the GitHub URL. Then I configured my custom domain from Godaddy to my repository and I believe it's properly configured because when I go to my custom domain in the browser the title appears in the browser tab, however no content is being rendered on the screen. It's a blank page. Any guesses on what the problem could be is much appreciated. The domain name is "connorjaksik.com"
Originally I didn't set up the DNS records properly on "GoDaddy".
I didn't add a CNAME with a value of my GitHub account username.
After that I noticed the domain was reaching my repository on github, but not rendering the content.
I had to change the repositories package.json "homepage" setting from the default, to my custom domain.
The source HTML code for your blank page shows "http://parked-content.godaddy.com/park/...", which means the redirection is not happening and Godaddy provides a placeholder page in the meantime.
Check your DNS provider settings, as explained here: it needs to allow "Naked" CName records in order to redirect your GitHub pages to a all domain name.

Firefox: "Some parts of this page are not secure, such as images." What counts as insecure?

I use the browser Firefox, and sometimes, on certain webpages, the SSL icon says "Some parts of this page are not secure, such as images." What, exactly, counts as an insecure element?
Thanks!
Anything that is delivered over an insecure channel.
What this generally means is that the developer of the web page is combining HTTP-based URLs with HTTPS-based URLs in the same page. The URLs could be for images as well as JavaScript, CSS, or anything else that can be referenced from a web page. As a user, there's not much you can do about this -- it's a warning that there is a possibility that your data could be delivered to other servers in an open, unencrypted manner over the Internet. This is a Bad Thing, but you can't do much except avoid that site, or contact the support or webmaster for the site.
If you're the developer, most of the time you can use a scheme-relative URLs when referencing images or javascript, etc.
i.e. Instead of this:
<img src="http://example.com/dot.png">
use this:
<img src="//example.com/dot.png">
YMMV.
See also: https://url.spec.whatwg.org/
In firefox you can see in Inspect Element=>Network Tab=>Domain Columns.
And also please check in Console tab too.
I hope it will solve your problem.
"Insecure" simply means "not loaded via HTTPS".
This is insecure:
<img class="media-object" src="http://placehold.it/50x50">
This is secure:
<img class="media-object" src="https://placehold.it/50x50">
"Some parts of this page are not secure, such as images."
means not all content are are loading with secure https you can use this online tool to determine which resource is loading with http whynopadlock
This is My Solution
To resolve this issue make sure that the page code does not pull data directly from a non-secure URL.
View the page source html code to check for non-secure items. This can be done in a web browser by doing a right click and selecting 'view source'.
To identify non-secure elements view the source code of the page and search for the text src="http://
This will then highlight elements on your page being loaded from a non-secure URL.
The source code (HTML) needs to be checked for NON SECURE tags. (i.e. http://www.symantec.com/images/seals/Secure...) Ensure the following references are changed to HTTPS or a virtual directory.
Note: The webmaster should always be consulted prior to any adjustments made to a web site.
Thank You and I hope this will Help out
For wordpress users that can't find any 'http:' in the page source check if you have a favicon set. Wordpress will default to their W icon (w-logo-blue.png) and I've had a couple sites continue to serve it from http even after fully converting to ssl.
Dashboard -> Appearance -> Customize -> Site Identity -> add a site icon
FOR IMAGES
First of all, check whether your image file has HTTP instead of HTTPS if so change it to https or rather save those images and put in in the Server.
For instance,
<img src="http://example.com/images/image.jpg">(http image source)
to
<img src="https://example.com/images/image.jpg">(https image source)or into
<img src="//example.com/images/image.jpg">(server image)
Firefox throws an error when you have mixed active content. This is having a combination of HTTP and HTTPs requests; it's a security issue as it leaves room for man in the middle attack- intercepting HTTP content requests with malicious or unwanted requests.
Tip: Check all the following urls in your active content:
< script >
< link >
< iframe >
< XMLHttpRequest >
fetch()
urls in CSS (#font-face,cursor,background.image)
< object >
Navigator.sendBeacon (look for url)
Another tip: make sure to check all files (css gets overlooked)

Unable to show page in iframe in Ektron CMS

I am working on Ektron 8.6.0.060 CMS, on admin dashboard I add an custom widget in which I call an iframe for content page, on picking URL from iframe, 404 page not found error occurs. All URL and signs are using correctly still error occurs.
Be sure that you are entering a fully qualified domain name in your IFrame. Unless you are very careful about your paths, relative locations will likely be incorrect. Rather than "/page/item.aspx" or "www.site.com/page/item.aspx" make sure you include your protocol, e.g. "http://www.site.com/page/item.aspx" . This is particularly easy to forget if you are generating this url dynamically.
Also, if you are pointing to ektron content, make sure the content is published and public.

SSL and Non Secure items message

I am seeing the "This Page contains both secure and nonsecure items." message when viewing a page on my site from with IE 6. This does not appear in both IE 7 or Firefox. I have done some research and it appears that the problem has to do with links to HTTP:// rather than HTTPS://
Would the fix just be to view the page source and find everywhere there is an HTTP:// src and change it? I believe they are being generated from JavaScript.
Thanks Nick
Yes, you need to make sure that scripts and images are referenced via HTTPS, if the page is referenced by HTTPS.
Alternatively, try using relative URLs, so that your page can be either HTTP or HTTPS without requiring the html to change.
Are you running prototype.js?
There's a line in there to detect when the page has loaded which calls \: as a src=
Replace this src with a js file on your system. It can be blank.
SO the problem was that a 3rd party control was creating an element with and attribute src="about:blank". In IE6 this src is not trusted. The resolution for me was to create a blank.htm file. This file contained nothing but an tag.
I then set the
This fixed the issue. From what I have read, this is not a problem in newer versions of IE.