Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
When we click on the SDL Tridion button in IE browser, it is redirecting to servername/WebUI/Editors/SiteEdit/Views/Editor.aspx with page not found message. But in Firefox it is working perfectly and Redirecting to servername/WebUI/Editors/SiteEdit/Views/Editor.aspx#url=https%3A%2F%2Fdev.view.mysite.com%2Findividual%2FnewUserInterfaceDemo%2Findex.html%23Basics.
Please help me in this issue. Any configuration is there for IE browser?
I see your preview site is on https. Do you have proper SSL certificate installed. IE9 throws a warning if you have any self-signed or invalid certificate and does not let you continue further unless you accept the risk.
First, try on http and see if it is working with out https.
(OR)
Try loading the self-signed certificate to your IE 9 browser and check again.
Reading the prerequisites for UI at (http://sdllivecontent.sdl.com/LiveContent/content/en-US/UIU4SDLT2011SP1/reference_339904289670453B90BED5AEB7258EB8 requires log in), IE8 is not supported anymore, so perhaps focus on IE9 for now..
Are you using HTTP or HTTPS? It looks like HTTPS, so you may need to sign the certificate as noted in this section of the documentation: http://sdllivecontent.sdl.com/LiveContent/content/en-US/UIU4SDLT2011SP1/task_A56C7DD930D14BAB9C2C30C40D29747A (also requires a log in)
Can you access the regular Content Manager Explorer with those browsers?
Try deleting ALL the cache in the browser including passwords etc, close it and try again. This may be some kind of cached value causing your problem.
There is nothing specific to Internet Explorer in the code, so something else is going on.
Please contact Customer Support instead for help on this issue, as it is not an appropriate question for StackOverflow.
Related
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 1 year ago.
Improve this question
I am using Cloud Run to run my app and I have it connected whit firebase, today I update a new version on Cloud Run, all perfect, I go to the URL and all my changes there are whit any problem, but when I go to my custom domain, I see the old version of my website broke, without CSS
I wear it because when I go to the link that CLoud RUn gives me, there is the new version without problems
Have you tried force refreshing your cache?
When you update a site and you see the active changes on some of it's URL access points but not all indicate that there is a cache in the middle. you can force clear your browser cache with F5, but if you are using a DNS cache like Cloud Flare, you will have to manually dump the cache from their services as well.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 8 years ago.
Improve this question
Recently, we noticed that CSS fails to load on IE9 over SSL, is there a way to fix this issue? We're using asp.net and IIS. Is there some setting that needs to be done to fix the issue?
This happens because mixing http and https content in the same page can sometimes be a security risk.
To fix it, either specify that the css always be https, or (better) use Schema-less URLs. A schema-less url simply omits the "http:" or "https:" part of the address. Instead of something like "http://www.example.com/style.css", you do this: "//www.example.com/style.css".
More info here
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 6 years ago.
Improve this question
I am developing a contact form on my wordpress blog on a windows server(not for my choice...).
I am having trouble to make wordpress send email.
I've been using most popular plugin for this (Such as Grunion Contact form and Contact 7), all working on my preview machine(Linux based).
Anybody knows about this issue? is it a php server configuration?
The SMTP issue has become a lot more common for sure. As another option to CF7 with Postman, you could use Formstack instead. Formstack gets around the SMTP issue perfectly, without the need for additional plugins.
All forms can have periodic sending issues, which can be super annoying. Formstack has been awesome, but we did encounter a recent issue, which related to a client's mailbox, so it could be worth a read to help you. The form wouldn't send (although it did store all the submissions) and this was triggered by a periodically full mailbox. The result was the client's email got blacklisted.
Check out our trouble shooting article about Formstack Emails Not Sending. Even though it's Formstack specific, I have a feeling this could affect other forms too, so it could come in handy.
A great plugin that helps you diagnose these issues and even give your CF7 plugin another mail engine to use is Postman SMTP: https://wordpress.org/plugins/postman-smtp/. I use it in conjunction with Contact Form 7 with great results. It will create a php mail engine for you if you need one/haven't built one already.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
What is the best practice to inform users if the services is down? In my example it's an application upload function that may be over capacity.
Thanks.
Uli
There are many ways that this can be accomplished and it all depends on what best fits your particular application.
If all you are looking to do is disable a feature, like in your example of disabling the upload feature, you could put a prominent message at the top of that page that says that it is not currently available and then disable the upload button on that page.
If you plan to take down the whole site for maintenance, it's good to have it as a separate page that is not linked to the rest of your site in any way. That way you can modify anything within your site, and also make a lot of changes to your web server.
Have an error page that is pure HTML - that way if the database goes down, you are not showing an error page that is dependant on some kind of DB query. Otherwise, your error page, will error.
You could return an HTTP error code if it is a web/http upload endpoint.
In our company, we have a procedure that do something like that (on our apache server):
Stop a particoular service
Enter .htaccess and do a rewrite-url to a standard down page
When we came back:
Enter .htaccess and remove the rewrite-url
Restart services
This is done by a bash script called when we want to shut down some services.
You could do that with a demon that check if server is "overlogged" and starts that routine.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I have an aspx website on IIS 6.0 which has the address https://www.website.com
I have made a virtual directory under this called cvr, which I am redirecting to http://servername:8080/websitename
Is there a way to keep https://www.website.com/cvr in the address bar after navigating to it? As soon as I hit the website, it shows http://servername:8080/websitename in the address bar.
Both sites are on my company network and the https:// website has a certificate, so is accessible through the firewall.
The answer is probably easy, but haven't done it before. Any help would be appreciated.
Si
Are you trying to do this in strictly IIS? If so I dont believe you can do that. If you are using .NET code you can do a Server.Transfer and it will keep the URL that is has. I wonder if you could just have a default.aspx where you can do the Server.Transfer.
In case you didnt already know a Response.Redirect means, tell my browser to request this page. A Server.Transfer your server says, "I know what page you want, ill go ahead and serve that too you so, dont have to make an extra request" and the side effect of that is the URL stays the same.
The best bet would be to setup a reverse proxy fronting both sites and then redirecting as needed.
In general, doing some voodoo to keep the same name in the URL bar is frowned upon by everyone . There is this thing called phishing that is real unpopular these days . . .