Problems after upgrade
By Zeosing on Thursday, 21 November 2013
Posted in Technical Issues
Replies 15
Likes 0
Views 1.5K
Votes 0
We have some isisues after upgrade to latest version:

1 - First

Warning: preg_match_all() expects parameter 1 to be string, array given in /var/www/vhosts/zeosing.com/bt.zeosing.com/components/com_easyblog/helpers/audio.php on line 36 Warning: preg_match_all() expects parameter 1 to be string, array given in /var/www/vhosts/zeosing.com/bt.zeosing.com/components/com_easyblog/helpers/audio.php on line 36 Warning: preg_match_all() expects parameter 1 to be string, array given in /var/www/vhosts/zeosing.com/bt.zeosing.com/components/com_easyblog/helpers/audio.php on line 36 Warning: preg_match_all() expects parameter 1 to be string, array given in /var/www/vhosts/zeosing.com/bt.zeosing.com/components/com_easyblog/helpers/audio.php on line 36 Warning: preg_match_all() expects parameter 1 to be string, array given in /var/www/vhosts/zeosing.com/bt.zeosing.com/components/com_easyblog/helpers/audio.php on line 36 Warning: preg_match_all() expects parameter 1 to be string, array given in /var/www/vhosts/zeosing.com/bt.zeosing.com/components/com_easyblog/helpers/audio.php on line 36 Warning: preg_match_all() expects parameter 1 to be string, array given in /var/www/vhosts/zeosing.com/bt.zeosing.com/components/com_easyblog/helpers/audio.php on line 36 Warning: preg_match_all() expects parameter 1 to be string, array given in /var/www/vhosts/zeosing.com/bt.zeosing.com/components/com_easyblog/helpers/audio.php on line 36


I donwload and upgrade the file audio.php from this post Audio but now widgetkit doesn´t work at all, worst solution than the original problem

2- Second

TypeError: style.test is not a function

/plugins/system/t3/base/js/off-canvas.js

Line 134


This error involves Easy blog, beacuse only happens when easyblog load it´s scrips in other pages the off-canvas navigation works fine, and of course we need no mantain the off-canvas navigation.
Hello Zeosing,

Sorry for keep asking you test it, because the js file can't edit in your FTP
You try add this code in your file again and see how it goes. 


 $this.data('opos', opos).data('otop', otop);

                        $this.css({'position': 'absolute', 'top': ($(window).scrollTop() + $this.css('top').toInt()) + 'px'});

Change to


 $this.data('opos', opos).data('otop', otop);

                        $this.css({'position': 'absolute', 'top': ($(window).scrollTop() + parseInt($this.css('top'))) + 'px'});
Arlex Wong
·
Thursday, 28 November 2013 13:51
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Zeosing,

Hm, I don't see how the second issue is actually related to EasyBlog because style.test is not something that is in EasyBlog and furthermore it seems to be pointing to the t3's script.

However, when I access your site, I don't seem to see any errors though. Did you already fix this on the site?
Mark
·
Thursday, 21 November 2013 23:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi , mark , the second issue is releted to easy blog due to , this isse only happens when easy blog load it´s scrips , in other pages when easyblog doens´t load any scrip the navigation works fine, so there is a scrip in easy blog that causes this error, we test the site carrefully and the only option is there is a scrip that load with easyblog that causes that error.

The other error were corrected

Thanks a lot for all the help.
Zeosing
·
Friday, 22 November 2013 02:56
·
0 Likes
·
0 Votes
·
0 Comments
·
Hm, I don't seem to see this error anywhere on the site. How do I see this?
Mark
·
Friday, 22 November 2013 03:08
·
0 Likes
·
0 Votes
·
0 Comments
·
Go to the main page, resize de browser windows to 767 px or less , cilck in the left top corner of the window to display the off-canvas navigation.

In main page doens´t work due to this scrip conflit , in other pages like "contacto" works fine.

Thnanks a lot for the help and your time.
Zeosing
·
Friday, 22 November 2013 03:28
·
0 Likes
·
0 Votes
·
0 Comments
·
I can confirm a similar issue. I'm using the T3 framework (latest release) with off-canvas navigation enabled and it works fine on all pages except the Easyblog page(s) which raises the following error in Chrome's Inspector:

Uncaught TypeError: Object 0px has no method 'toInt'


The script is being loaded from the T3 framework but only conflicts on the EasyBlog pages. I've tried jQuery easy to resolve the conflict but had no joy and I also tried disabling EasyBlog's own "Enable responsive" setting but again no change.
Simon Logan
·
Tuesday, 26 November 2013 22:50
·
0 Likes
·
0 Votes
·
0 Comments
·
Any Idea of this ?
Zeosing
·
Wednesday, 27 November 2013 21:51
·
0 Likes
·
0 Votes
·
0 Comments
·
We're still checking this, will get back to you once we figure this out.
Mark
·
Wednesday, 27 November 2013 22:41
·
0 Likes
·
0 Votes
·
0 Comments
·
Ok , no problem, take your time, there is no hurry with this, thanks a lot for the help, and all your work
Zeosing
·
Wednesday, 27 November 2013 22:54
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Zeosing,

Regarding on your left top corner of the window to display the off-canvas navigation issues :
Could you have a try edit this code in your file and see can work or not?
JoomlaFolder/plugins/system/t3/base/js/off-canvas.js


opos = style && style.test('position') ? $this.css('position'):'',

otop = style && style.test('top') ? $this.css('top'):'';

Change to


opos = style && style.match('position') ? $this.css('position'):'',

otop = style && style.match('top') ? $this.css('top'):'';
Arlex Wong
·
Thursday, 28 November 2013 12:27
·
0 Likes
·
0 Votes
·
0 Comments
·
I did the changes but another error appears:

TypeError: $this.css(...).toInt is not a function

/plugins/system/t3/base/js/off-canvas.js

Line 138


Thanks for all the help.
Zeosing
·
Thursday, 28 November 2013 13:24
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks a lot, great work, and great support team, works fine

Thanks again.
Zeosing
·
Thursday, 28 November 2013 14:52
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Zeosing,

You're welcome, glad to heard your issues resolved.

===============================================================================================================
Hello Simon Logan,

You can follow the above instruction to solve your problem. Please let us know if you need further assistance.
Arlex Wong
·
Thursday, 28 November 2013 15:51
·
0 Likes
·
0 Votes
·
0 Comments
·
Yeah that works perfectly for me too, thanks for that (particularly since the fix wasn't applied in your component!)

Will need to stick this fix in Evernote as I have a feeling future updates of the T3 framework might overwrite this and bring the problem back. Will also maybe get in touch with the JoomlArt guys to see if they can sort.
Simon Logan
·
Thursday, 28 November 2013 19:50
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Simon Logan,

You're welcome, glad to heard your issues resolved.
You're right. Actually you can report to them about this case and see how it goes. Maybe they will take action.
Arlex Wong
·
Thursday, 28 November 2013 23:09
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post