All the pages on the site are set with the default 0.5 priority and the site map settings are even set lower to 0.1 just to be sure this isn't the issue but still only a few pages are generated in the sitemap.
I've tried clearing the app cache and restarting the app pool but still no luck.
https://www.tompkinsinc.com/sitemap.aspx
This is cached in the portalid-system folder under sitemap. I’d suggest trying to delete that file first and see if it’s better.
Related
We have some medium website (> pages) and would like to prerender the entire site. Upon content changes in some external system, we would like to update only the specific page which contains the updated content and deploy the updated version of the page as static html page to some publishing service (webserver, CDN, Netlify, etc.).
I have seen that SvelteKit supports this SSG rendering approach through the adapter-static but as far as I've seen it always builds all the pages/routes for every build. This is currently a blocker because if an editor updates some content it takes more than 15 minutes (rough estimate if you have around 1500 pages) to see this update online.
Is there already some possibility to simply build some specific page or route?
Looks like that this is still an open feature request and to be discussed there: https://github.com/sveltejs/kit/issues/2369
I'm currently using Google Appengine to host a website with Golang as the backend. I have a custom domain setup and (sometimes) it works perfectly fine. My website requires some css and js files from the server. These were served perfectly in the past but now it randomly stops working. Both on the "mydomain.de" and on the "myapp.appspot.com" domains. Sometimes it works on the normal domain and then it works on the other and sometimes even on both. But if I reload the site after a couple of minutes it just shows me an old index.html file (that I have removed days ago).
Did someone experience this problem in the past and does anyone know a fix for this?
Thanks in advance.
Have you ruled out your browser cache as the source of the problem? If after getting a stale version, shift-reload (assuming Chrome or Firefox) brings up the desired version, then look into how to do "cache busting" for css and js, and check the app.yaml doc for how to set expiration times on static assets (assuming your index.html is static).
We are deploying a CakePHP application to nginx(1.2.4).
There was an issue with the view files, it does not refresh the latest view files.
It seems like the views are always cached, and I have to clear the browser cache in order to load the updated content.
I tried to disable in CakePHP, but the problem remains.
Anyone encountered this issue before?
EDIT
At the end, we figured that it is causing my the conf file under site_ available folder
http://book.cakephp.org/2.0/en/controllers.html#Controller::disableCache
http://book.cakephp.org/2.0/en/controllers/request-response.html#interacting-with-browser-caching
Check if you set debug to level to something different than 0. Debug level other than 0 sets cache for couple seconds automatically so you should be able to see latest changes for your views.
i need to remove sitemap.aspx from the site.
In dnn 6,there is a sitemap.aspx page that simply shows an xml sitemap.i cannot edit/remove that file.so i need to remove that page and recreate it with a simple html sitemap.
NOTE:the page name should be sitemap.aspx
Sitemap.aspx isn't a physical page you can delete.
You can, however, rename it to something else. It's in your web.config file, under the 'handlers' section. Just look for sitemap.aspx, and change it to something else, like 'searchenginesitemap.aspx'. Don't forget to update your robots.txt file to point to the new sitemap name, or go to the various webmaster console pages in search engines and advise them of the new location.
The sitemap.aspx is used to create the xml sitemap for search engines. By changing this you break this functionality and limit the search-ability of your site.
That being said, in Host Settings->Advance Settings you could setup a new Friendly Url that would match .*/sitemap.aspx to another url/page on your site.
I have long stopped using DNN's native sitemap.aspx... ITS BUGGY!... and here is how i found out.
I generated my own "CLEAN" sitemap.xml using a free 3rd party tool. And uploaded it to the root of my DNN website.... re-submitted the the domainname.com/sitemap.xml to Google via web master tools and as a result we now get a 1ST PAGE and TOP 10 RANKING.
Mostly in the top 5... where as before using DNN's native sitemap.aspx we would get random errors which was pretty ANNOYING. Plus we got very bad Google Page Rank, But those were just my findings of better results. Note:I also place the location of the sitemap within the robots.txt file...
Although i will admit that it is extremely ANNOYING that you cannot just edit the DNN Sitemap url. This creates an issue if you've built the the site on a test server and then migrate over to production... your DNN Sitemap url only reads the firs portal alias from when you first developed the site.
Anyway, this was my findings... others may vary... just sharing.
I'm managing several DotNetNuke portals (as well as the main hosting itself). All of the portals have the default DNN icon in the address and when they're bookmarked. I want to have a custom favicon.!
It's the icon on the left side of this:
(source: dotnetnuke.com)
I've tried clobbering the default favicon.ico file in the root directory (where the web.config file is located). I've deleted, I've replaced, I've restarted the browser, I've bounced IIS. None of that works.
Has anyone come across a solution for the wonky favicon problem in DNN?
Times have changed in the DotNetNuke world since this question was answered. Now, the favicon is much easier to change.
Go to Site Settings underneath the Admin menu, and scroll down to Appearance. There should be an option to upload a new icon, or use one currently on your site.
You need to place the favicon in each portal's own folder (Portals/0/favicon.ico). Make sure you delete the icon in the root of your website, as that will (supposedly) override any portal-specific favicons and apply to all portals.
Have a look here as well: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/108/threadid/183454/scope/posts/threadpage/3/Default.aspx.
Favicons are notorious for being very aggressively cached by the browser. Sometimes even clearing the cache doesn't even do the trick, it can drive you mad. Clear cache, shift-refresh etc etc...
Have you tried clearing your browser cache? Or try using a browser on a different machine or just a different browser (FF versus IE for isntance). The favicon will cache and drive you crazy when it actually has changed.
The other thing to check is to see if you have more than one portal running on your DNN instance. If you have more than one portal, you can do a different favicon for each portal by putting the favicon in portal root and not the main web root.
http://www.hanselman.com/blog/FavIconicoCanBeABandwidthHog.aspx
Worth reading for performance purposes.