My Nivo slide transitions were working in an earlier iteration of this test page. But now I see they aren't working, the slides are no longer functioning as links to other pages like they should, and the captions are appearing about a second before the slide. I have gone over everything with a fine-toothed comb but obviously not fine enough.
The page in question is:
http://americanart.si.edu/index_new_prerelease_jeff2.cfm
Any help would be appreciated. Thanks
I scanned your HTML and Javascript and the only thing I can say is, you have an error on jTweetsAnywhere. It isn't uncommon that if one function, no matter where, gives an error, other stuff stops working too.
So try fixing that error first, or commenting out the jTweetsAnywhere initiation as it isn't recognised ("has no method 'jTweetsAnywhere'")
Related
I have a problem with using Bootstrap plus Masonry for my layout. Trying it out on my computer, it works perfectly, but when I upload it to GitHub pages or Godaddy hosting, it sometimes gets destroyed like the image I shared. I bought Lightgallery and tried it instead of Fancybox to make the photo gallery, just in case something there was making a problem, but it's the same.
The problem being Masonry or bootstrap, I can't get rid of bootstrap but could use an alternative to Masonry. My client just needs the Pinterest-like layout.
It's very frustrating because it works perfectly until it is live. I tried a lot of things but nothing has worked. Thank you for any idea you could give me, and sorry for my bad English.
Github link: https://m-ribero.github.io/mubles-ballena/galeria.html
edit: Very important detail, it often gets fixed after reloading or resizing the page, but for the first time someone enters there, then it doesn't motivate people to invest more time in the site if it looks that bad.
gallery destroyed
gallery destroyed 2
The problem is with Masonry and not Fancybox (or any other lightbox alternative). Looks like it incorrectly calculates height for the container. Since it works after assets have been cached, I guess that your masonry script does all calculations before your CSS is loaded. Therefore top/bottom padding is not taken into account for calculations.
I've tried all the troubleshooting suggestions, and I've got iFrameResizer working on other sites without any issues, but it's snagging on this one and I can't fathom out why. Weirdly, it works on the details page, but not on the listing page. Logging returns the
"hasn't responded in 5 seconds" message.
I've also tried all the various triggers ('max' etc.) none of them make a difference.
Example page where it doesn't work:
http://www.homesinfocus.co.uk/properties-to-let/
But on the details page, it does work:
http://www.homesinfocus.co.uk/property-details-let/?ID=790&LB=Let
I've made sure all the iFrames have unique IDs, and the listing page works okay for other sites, just can't see where the issue is with this one.
Any pointers would be much appreciated.
David, thanks for your help. CheckOrigin seems to have fixed it.
Seems to work fine with the following:
<script>
$(window).on('load', function (e) {
$('iframe').iFrameResize({checkOrigin:false});
});
</script>
The most common reason for that, is that the iframe hasn't loaded it's js file.
Also check that your using the very latest version, as the error message gives a bit more detail.
I am trying to port over a bit of code from wx2.8 to wxPheonix (3.0.3.dev78356 msw). I'm using code from the pyfa project (https://github.com/DarkFenX/Pyfa) which is currently being rewritten for python3. This code takes some concepts from PyCollapsiblePane and implements it better (there are some bugs with PCP). If you download and open pyfa, the collapsible panels are on the right side (resources, resistances, etc) if you want to get a feel for how it is supposed to work.
Anyway, I'm trying to port this over and I cannot seem to get it to work well. I know Pheonix introduces some changes to sizers and how things are resized. I am able to collapse the panel (and have the parent panel fit to the new size), and then open it again. But when I try to collapse it again nothing seems to happen.
Here's what is currently happening:
http://gyazo.com/68717f66c498d850ef60ee83e1c0ae4a
And here is how it's suppposed to work (wxPython 2.8 in the pyfa app)
http://gyazo.com/87cc0f61052dca0e81c387da0f84c0c4
This is the module that I'm working on (the script has a test case if run directly): http://pastebin.com/ghuVGXWN
Any ideas?
I had to remove self.SetMinSize(sz) from OnStateChange, works great now.
I have been working on this site for some time and just launched it for a client.
People have actually had trouble beleiving I had done it on WordPress, though I don't see why...
Anyway, I suddenly see that the form fields of one of the forms on the site (Newsletter Registration) disappear while on IE, you get to see them for a second and puff, they're gone. I did check this previously on IE and it worked, I especially used CSS3 PIE to get the rounded effect for the fields on IE...
Link to website: http://www.doritsivan.com (hope this isn't considered promotion, not my intention)
site is based on WordPress and jQuery.
resolved the issue, thank you all. it was a bad case of relative vs. absolute positioning and the fields decided to go away (literaly)
A bunch of debugging with firebug-lite (btw was real to get it to work on my IE, kept on crashing or refusing to load altogether combined with IE popup and security issues) and I understoid that this was the issue, then some pixel fiddling and all was good. rechecked in Chrome, saw that result was exactly the same. job done
I'm learning how to use Draggable Views for Drupal 6 for the first time, following this tutorial: http://thedesignspace.net/MT2archives/000666.html . I'm encountering a problem though: in part 4, once I set up the draggable table ( http://thedesignspace.net/MT2archives/000708.html ) the entire preview disappears, showing no table. Switching the style to another type, such as table, brings everything back. Directly viewing the page from its path makes no difference. Any ideas of what the problem could be?
Not all of my modules were up to date when I encountered this problem. My mistake. Always update all modules first upon being stumped by incompatibility errors, even if the modules in question do not seem to have anything to do with the error.