htb
(@halinasplace)
got it working not in a post but a page
http://blog.halinasplace.net.au/blog/test-3/
now I’ll do some formatting of the css
htb
(@halinasplace)
weird behaviour with default template – the styling seems to change on a refresh of the page – can’t seem to find the problem
http://blog.halinasplace.net.au/blog/test-3/
before I use this as a default and copy t to make another one would like to get the default working properly
It might be not the Style, but on some page realoads the javascript isn’t loaded. It contains by now a little jQuerry snipplet to give all blocks the same height.
Maybe a .block{ height: auto; } can help when javascript is disabled?
Please let me know if you find
The REST-Api Key you find on your G3-User Page. Login to g3 and klick on your nam at the top-right (using default theme).
@shecter:
halinasplace is right. I thought I solved this issue in 0.8.3 .. but now again 🙂
In General:
There are still some issues about updating the caches. If you have unexpectable behavior safe WPG3 Options page at least 2 times. It might help.
@halinasplace
Thanks for your comments. I’ll see if I can keep my promisses to enable integration in posts too in next release.
I’m heavily working on the Insert-Image (imagechose) and an additional (default)-Inline-block-template now.
@halinasplace:
you should use jQuery( … ) instead of $(…) for jQuery in WP. It runs in No-Conflict mode.
Check you Javascript-Error console. It might resolve some strange behavior.
htb
(@halinasplace)
I have plenty of warnings in my error console it would be hard to say where the conflict is…. I do however have this statement in my themes default css
#content .post .gallery {
overflow:hidden;
}
I’m playing around with it at the moment
Just solfe the Errors. You hardly will find any application without warnings. WordPress isn’t, due to workarounds. e.g. there are at least 3 ways to get rounded corners and for the not-firefox-ones (-webkit …) you’ll get a warnig too.
But some of your Javascripts drop errors. Make sure you don’t have errors to have a predicable testing environment.
I added a <div class="clear"></div> into this template for the next release to stop the floating after the gallery. The overflow: hidden dosn’t make sense for me at this point, but maybe for you 🙂
htb
(@halinasplace)
Error: $(document).ready is not a function
Source File: http://blog.halinasplace.net.au/blog/test-3/Postcards/
Line: 227
when running your script – so how do I solve this again running jquery instead of $(…) – how do I go about doing that ? sorry I haven’t come across this issue before….
htb
(@halinasplace)
never mind – I’m solving the errors – but when it does work I notice if I have albums nested within each other then it doesn’t go down another level
eg if you try out and go to postcards there is another subalbum – clarendon st – if you click this – it doesn’t go to the sub album
htb
(@halinasplace)
Well I’ve cleared all the errors and I’m still getting the same problem with your jscript not being called unless I do a refresh – I’ll keep looking – any hints?
There is a inline style style=”…”
One time we load is’s
height: 60px; width: 110px;
which looks odd. Another time:
height: 244px; width: 204px;
which looks correct. maybe it is my javascript that causes the issue. (try disabling it). But
I think it is this:
jQuery(document).ready(function(){ $("a[rel='zoom']").colorbox({slideshow:false,transition:'fade',maxHeight:'70%',photo:true });
});
you have to replace EVERY $ with jQuery read here: http://codex.wordpress.org/Function_Reference/wp_enqueue_script#jQuery_noConflict_wrappers.
So maybe sometimes firefox continuos the script, sometimes not.
htb
(@halinasplace)
I’ve removed that code (jQuery(document).ready(function(){ $(“a[rel=’zoom’]”).colorbox({slid etc)
it was causing errors
but when I clear the firefox cache it works for a little while on the first album….
ps you mean I have to go through all the javascripts and all the code and replace it – thats a lot of work
htb
(@halinasplace)
so the first album always works properly and subsequent albums do not.
also nested albums don’t work either ….hope this helps a little further!
Maybe there is an issue, because the Album and Subalbum name are the same.
In next release I will include some more debug info about the request. I can not see what is happening without adding some print_r for the request or $slugs.
The Request is handled WPG3_Rewrite::page_content_filter() if you wanna dig deeper.
With my local test installations Subsubsubalbums work well.
htb
(@halinasplace)
your slugs don’t seem to be the issue as it is picking up the write url and rewriting it but the album content is wrong – I’ve put print_r in various places and it shows up ok – any requests on where to put the print_r in the code?
htb
(@halinasplace)
the wrong parent is being passed to the album template:)
