I have somewhat bizzarre situation... on my localhost when I debug the project all the pages are visible and first page (default page) is visible upon startup.
When I publish the project and move it to server all the pages are accessible and visible except the default (Home/Index).
My global.asax is ok, nothing is reporting any errors but when site is opened only the blank page is visible.
Could this be something with IIS? Since it's configured normally and we've event applied that hotfix for displaying pages without extensions (but it didn't work before that, tho).
Related
I have 2 webapplications build in vue. One application is some sort of wrapper for all the applications a company has and it loads several projects via an iframe (And one of them is the other web-application build in vue).
Both projects have the vue-pwa plugin installed.
When opening the wrapper project in the safari browser on a mac and browsing to the iframe with the other vue application the screen is blank and i'm seeing that there are an unlimited count of console.logs: Service worker has been registered. from the register hook in the registerServiceWorker.js
The moment i open the contents of that iframe in a seccond tab of safari, these console.logs stop and the page is normally loaded and functioning.
Does anyone have an idea for a solution, or how to debug what the issue is?
The issue was that i needed to set the header X-Frame-Options: ALLOW-FROM https://example.com/
Weird thing is that the code was executed, it was just not visible. And other browsers don't seem to bother that since there was no X-Frame-Options that blocked it.
So, I'm building an application with Vuejs and after we finish her we decided to finally build for production. Everything worked just fine while building and etc, but when the application was really being hosted, we noticed some issues that we do not saw while on localhost (development and production).
I'm saying this after a lot of tests and researches about it because first, I thought that the problem was after building to production but we tested another way to host and it's not apache that is causing this issue and I really think that is not the code either. Anyway the problem is when we first access the application our login page is the first that you can see and it works just fine at the first access but if the user refreshes the page for any reason the page loses all her CSS because the route /auth/login goes to /auth/login/ and after some tests I can confirm. That bar that is added at the end of the route makes the page lose CSS.
This problem we solved by adding an exception on our .htaccess (we know that this is not that best practice but anyway) after this solved we saw another problem: when we click on a link for example /auth/login?token=12334567890 the token param simply disappear and the user is automatically redirected to /auth/login. So we think that maybe these two problems are related because when we first access and log in everything inside the application works as it should, these two problems are only occurring on our login component. My question is what is causing this problem only on this page? It's a vue-router that is causing?
The problem is that site view in cms differs from live site itself.
In cms edit mode I've deleted component from container inside page, saved, then published changes. Publish done successfully without any errors and site view in cms looks correctly, i.e. without that component that was removed. But this component still appears in live site.
I can easily fix this problem by removing this component in console. In cms console it can be seen that preview and working configuration differs.
But why this type of desynchronization happens? And what can I do to prevent this kind of problems?
This type of desynchronization happens rarely, but this problem may be very critical in production.
I am using Hippo CMS 10.1.0 Community Edition
If Your configuraton have been resynchronized, good way is to remove whole preview node. This node will be reconstructed from Your live node when You enter in CMS and turn on edit Mode.
I am working with small application in SharePoint. I have a custom application page on which i am loading .ascx Control under Page_Load() method. .ascx Control is a small form with text boxes and a button. Now when i click on button, the information successfully saved in the list in SharePoint, but it gives Runtime error:
Description: An application error occurred on the server. The current
custom error settings for this application prevent the details of the
application error from being viewed.
Details: To enable the details of this specific error message to be
viewable on the local server machine, please create a customErrors tag
within a "web.config" configuration file located in the root directory
of the current web application. This customErrors tag should then have
its "mode" attribute set to "RemoteOnly". To enable the details to be
viewable on remote machines, please set "mode" to "Off".
I have checked my web.config, and customError tag is there and mode is set to "Off".
what is problem ? I want to stay on same page after clicking button.
It is definitely staying on the same page as asp.net page always posts back to itself only and redirects only if you explicitly ask it to do so. There is either some error in your code or in you web.config file.
Further the error is in the block of postback code
i.e. Somewhere on your page there is some code like
if (isPostBack)
{
**//Some code with error**
}
as the error occurs only when you post back.
I would suggest you go step by step debugging and pin point the exact line of error.
By using Response.Redirect(Request.RawUrl); solves the above issue.
I have as ASP.Net 4.0 application that I added a custom route table to in Global.asax. It was working fine for a while. I needed to change one of the routes to point to a new webpage and I did so in the route table but when I run the app - it still navigates to the old page. So I have been debugging to try and discover the issue and I have disovered two very strange things:
1) The code in Global.asax code is no longer firing. I set a breakpoint in Application_Start and then stopped the developement web serveer (VS2010) so that the app would have to restart and then ran the app - it never gets hit.
2) Even though the code does not fire - the routes are still there (pointing to the old page) - being cached somewhere?? I even rebooted the dev box but they are still there...
I scowered the app (team project) for any header files which can over-ride Global.asax and there are none. I don't know what to try next - any ideas?
Some new info - after googling around some more.
Stopped vs web server
Excluded Global.asax from project (Original code without changeing
rout to point to new page).
Rebuilt application.
Ran application and now all the routes are gone - cannot navigate to
any routed url's in app.
Stopped vs web server again.
Included Global.asax back into app.
Build again
Run again and now hits breakpoint in Application_Startup.
Stopped vs web server again
Made code change in route table to point to new page.
Excluded Global again
Built app again
Ran app again - routes gone.
Stopped vs web server again
Included Global again
Built app again
Now - breakpoiont not hit again and old route is back
AM I going crazy?