-
AuthorPosts
-
August 20, 2012 at 9:47 am #180066
Hello,
where can I find a complete changelog for 1.0.4 version of JA Wall?
Found this: http://update.joomlart.com/#compare/JATCWALLJ25/1.0.4/1.0.3
August 20, 2012 at 10:03 am #464744I’m still wondering if the issue with sh404sef pagination is fixed in this release. Anyone?
arucardx Friendarucardx
- Join date:
- July 2010
- Posts:
- 346
- Downloads:
- 0
- Uploads:
- 10
- Thanks:
- 21
- Thanked:
- 138 times in 104 posts
August 20, 2012 at 12:34 pm #464752I actually had a working copy of 1.03 after creating many tickets but I thought I would update to 1.04 so I looked thru the updated files for 1.04 and seems only these few things were updated. The update was successful though, all the fixes I requested for were included except those in template.css
JA Lazyload <– works with social sharing now by excluding indexing bots
JA Social Feed <– I dunno since I don’t use this.
JA Extension Manager <– dunno what was fixed here too, didn’t see any difference
wall.js <– contains fixes for IE9’s pop up cut off, scroll bar & infinitive scroll pagination
component.php <– was missing 1 div in 1.03
layout-mobile.css <– viemo style is fixed
template.css <– the z-index for a pager function was changed from 100 to 2000.
index.html <– Some new variable for custom loading msg without modifying wall.js and removal of facebook xml.
tag.php <– $item->introtext; changed to $introtext (that fixed a duplication problem in the demo)JA Pager didn’t get updated so I don’t think your sh404sef pagination problem can be fixed until then. Unless wall.js fixed that.
But I remember there was a post somewhere in this forum where a developer comment that there’s a conflict with sh404sef and the guy hired a freelancer to fix it and shared the fix. Though that fix caused some other problems instead. You can try digging around if you’re interested. But overall that’s what was fixed or changed in 1.04.
1 user says Thank You to arucardx for this useful post
August 20, 2012 at 1:27 pm #464759<em>@arucardx 335139 wrote:</em><blockquote>I actually had a working copy of 1.03 after creating many tickets but I thought I would update to 1.04 so I looked thru the updated files for 1.04 and seems only these few things were updated. The update was successful though, all the fixes I requested for were included except those in template.css
JA Lazyload <– works with social sharing now by excluding indexing bots
JA Social Feed <– I dunno since I don’t use this.
JA Extension Manager <– dunno what was fixed here too, didn’t see any difference
wall.js <– contains fixes for IE9’s pop up cut off, scroll bar & infinitive scroll pagination
component.php <– was missing 1 div in 1.03
layout-mobile.css <– viemo style is fixed
template.css <– the z-index for a pager function was changed from 100 to 2000.
index.html <– Some new variable for custom loading msg without modifying wall.js and removal of facebook xml.
tag.php <– $item->introtext; changed to $introtext (that fixed a duplication problem in the demo)JA Pager didn’t get updated so I don’t think your sh404sef pagination problem can be fixed until then. Unless wall.js fixed that.
But I remember there was a post somewhere in this forum where a developer comment that there’s a conflict with sh404sef and the guy hired a freelancer to fix it and shared the fix. Though that fix caused some other problems instead. You can try digging around if you’re interested. But overall that’s what was fixed or changed in 1.04.</blockquote>
Thanks, arucardx,
I went through all the changes myself. I’ve also tested the new version with sh404sef and so far it seems to be working ok. I’ll have to test it a bit more.
I’ve also noticed that using lazyload makes all the images like this:
<img style="display: block; margin-left: auto; margin-right: auto;" class="lazyload" src="http://www.my.com/cache/jalazyload/700x1011.png" longdesc="http://www.my.com/images/stories/image.jpg" alt="Mask 1" width="700" height="1011" />
When trying to share the article on facebook it takes the cache/jalazyload/700×1011.png image and not the real image that is loaded later by lazyload. Is there any way to make it load the correct photo?
-
AuthorPosts
This topic contains 5 replies, has 3 voices, and was last updated by Saguaros 12 years, 3 months ago.
We moved to new unified forum. Please post all new support queries in our New Forum