We're having a very strange problem with css in DotNetNuke.
It seems that with any of our custom modules, if a user clicks to postback 9 times the skin css is removed and the page becomes rather ugly. Looking at the source the tags with the urls to the css files are gone. After one more click making 10 postbacks, any custom css files we've added are removed as well. It seems that sometimes the css will come back after more postbacks but other times it will not.
what you click on doesn't matter, just the amount of postbacks. However we have another server that on some days will behave fine, and others will have the same behavior.
We can't narrow it down to anything our modules have in common. It happens in modules that do not share any code, but somehow happens in all our modules that we've tried but not in any other modules that come with DNN.
Though experimenting we've also found you can postback say 8 times leave the page and come back, you then can postback 9 more times before the css will be gone.
Something link this has happened to me before but not with dotnetnuke, so it may not apply.
Anyway, my my case what was happening was i was making an ajax request that would update a table body with some new rows. on some requests, the page would lose its css styles. it looked like no styles were used on the page.
the root of the problem was that invalid html was being returned from the ajax call. actually a 500 error page was being returned by the ajax, which contained HTML tags, the whole deal. this seemed to break the styles in IE.
if "postback" == ajax request, then this may help
This was do to not having a doc type set for the DNN skin we were using. The copyright was a side effect.
Related
I'm creating Views for an ASP.NET MVC application. I'm using _Layout and some other Views like Shop, Contact, etc., which have only one element: "content".
How can I set content change animation? I don't like white flashing while changing.
What you're seeing is unrelated to MVC and is the result of simple HTML page transitions. Since you're actually changing the entire page, the white flashing is the result of loading the new page.
You can manage this through CSS and jQuery. Here is one article that describes one way to manage page transitions. Just search for HTML Page Transitions and you'll see plenty of jQuery libraries made for this with extensive documentation.
Here is one jQuery library I found: Animsition
Some additional information on the white flickering you're seeing from this article.
Amongst the various problems with web page loading, white flicker is
considered to be one of the common issues which occurs during page
access, loading, reloading, and traversing Internet browsers. The
white flicker occurs for various reasons including the browser trying
to render the page before the style sheet has finished loading,
JavaScript issues and other rendering faults. Browsers will always
wait until everything (beyond images) has finished downloading before
rendering.
It depends of your css template, if It has spinners you should look in the documentation, if your template doesn´t have, look for one, there are a lot of template of spinners with documentation.
Here is an example of documentation (of course, this apply if you are using inspinia, but all of them have similar applications):
http://webapplayers.com/inspinia_admin-v2.8/spinners.html
I have a website in wordpress. I recently download a plugin called Advanced Ajax Page Loader. It refreshes you content when clicked on other page without refreshing the whole site(header, footer). I tried to get my answer from plugins developer and wordpress support forum, but none responded.
I read that if ajax jquery call is used then all scripts should be reloaded again, for that the plugin have a place where I should put those codes. Until that everything works correctly, except one thin. When I go from a category to category, everything works fine, but when I open a single Post it completely screws up all my css for that page, when I refresh it, everything looks fine but then again, if I open one of the big categories with many posts, then that pages css is messed up.
I though that I could somehow refresh whole css by putting some code in the "Reload code" box, but I have no idea how to do that using scripts. English isn't my native language, therefore I'm having difficulty finding my answer on google, I tried, but my vocabulary is limited. How can I do it?
are you adding CSS classes to your elements via Javascript? If so, then the styles you add will only affect those elements which are part of the DOM at that point in time, so you might be experiencing a race condition, that actually happens to work in Chrome and Safari, but not Firefox.
second try to validate your markup and CSS and see if you have any error in your css syntax ?
For some reason whenever I go to the page of my website that has the crystal report on it my main navigation bar disappears. Here is what the header for the site (with the navigation menu) is suppose to look like:
and here is what it looks like when there is a report on the page:
Could someone tell me what is causing this and how I can fix it?
I'm using master page for the header by the way.
Greener, the Crystal Report viewer is a dynamic HTML representation of the report. It combines JavaScript, HTML and CSS (duh, what doesn't) to represent your report on the webpage. The toolbars are powered by JavaScript calls to .JS that is linked in when the CrystalReportViewer control is rendered to your page.
My point is, all of this introduces a LOT of stuff that can conflict with your existing page. In particular JavaScript errors can occur (which can cause certain things to stop rendering) OR CSS the report uses happens to apply styles you never intended to have applied to objects in your page.
I highly recommend installing the Web Developer toolbar and/or FireBug to FireFox, IE, or whatever browser they are offered on these days. FireFox's implementation of those is quite good in my experience.
When the page loads you can use the 'CSS' menu of the Web Developer toolbar to actually disable some or ALL the styles applied to the page. If disabling Crystal related styles (or all) makes your missing toolbar appear, then it's probably a conflict in your CSS. A front end developer would know to adjust the styles (i.e. add the !important directive to a style, change class/id names, etc.) to address this.
Alternatively, FireBug may be reporting JavaScript errors (heck, even FireFox can show these in the console) which could indicate a problem that prevents the completion of rendering your toolbar.
An outside possibility is that the report itself contains mark-up. For example, if you had certain fields in the report contain HTML that happened to be rendered by the browser, this could create an open div tag, css styles and even JavaScript that would do all the stuff I explained above.
I hope this narrows it down for you. Happy troubleshooting!
I was having the same issue and after hours of searching I finally resolved it... check this out... http://scn.sap.com/thread/1926659
In the crystalreportviewer css file, I adjusted the div class = clear and changed the height attribute and disabled overflow:hidden. Hopefully, that works for you. Good luck!
I found the solution after searching on the web and is a quite simple.
On the Site Master, change the Name for all the places you have the style "clear" for example "clear1" and change it too en the site.css with that name.
The problem is for the conflic with the namespaces with Crystal Report css.
Hope this help.
This seems rather a common problem, however I can't find any reliable sources on this.
Once in a while Chrome will display a stylesheet-less version of page for like 2-3 seconds and soon after the page is displayed correctly. It can affect the very same page once in every 20-50 refresh and its not tied to a specific site. Happens all over the place. There are some threads about this here and there, but I have yet to find a full explanation.
Is this a bug? Feature? Is there a way to prevent Chrome from behaving like this on the client or perhaps server side?
In my experience, this happens when the network connection is poor and the page is (necessarily) loading slowly. The page's HTML will render first, and other assets called for within that HTML (like stylesheets or images) are rendered only after their calls are complete and their respective files load.
I have noticed this as well. It's definitely a bug. It seems to be this issue:
http://code.google.com/p/chromium/issues/detail?id=75761
You can "force" the stylesheet to load by opening the inspector (ctrl+shift+i).
shift + f5 should reload the page and the referenced stylesheets
With a normal reload it will only reload the page itself, and incorrectly assume that the stylesheets in the cache (the ones that never loaded in the first place) are correct.
This is basically a continuation of a question of mine from yesterday,
"Foregoing intialization on a page"
(And btw, kudos to all who give selflessly in this forum to help others - need to do more of that myself.)
So anyway, I was told about HistoryManager, BrowserManager and SharedObject, and so quickly ascertained that its no problem to store a few data items in a shared object so a flex page restores the previous configuration when the browser navigates back to it.
But my real concern would be speed of loading. Its a 15mb page and it only takes 2 seconds to load, but that's still not instantaneous. If it were in a tabbed browser and I just clicked on another tab containing my page, my page would then appear instantaneously. Is there any way to achieve that behavior when my page is navigated back to (via the browser back button for example.) Would that mean that the entire 15mb flex web page would have to be stored in memory.
Thanks.
Here's what I'm thinking, you're going the wrong way about this,(unless I missed the boad on what you want to acheive) what you need to do is work with javascript to interact with the browsers url. Thjis is assuming that you want to be able to go back on a page without reloading content.
Basicaly a java script would override the reloading, and when you hit back, the page doesn't reload, but the javascript notifies the flash what change in has occurred.
Have a look at the gaya framework for how they do it
or lookat http://www.robertpenner.com/experiments/backbutton/backbutton.html