11
colossus
HTML validation errors in Youtube tags
  • 2009/7/12 23:37

  • colossus

  • Just popping in

  • Posts: 43

  • Since: 2007/9/30


Hi:

In XOOPS 2.3.3 (and previous versions I guess), a post or comment that has some Youtube video embed with Xoopscode "Youtube" won't pass HTML Validation.

I think this can be fixed modifying line 75 in the archive class/textsanitize/youtbe/youtube.php:

$code "<object width='{$width}' height='{$height}'><param name='movie' value='{$src}'></param>" .
                 
"<param name='wmode' value='transparent'></param>" .
                 
"<embed src='{$src}' type='application/x-shockwave-flash' wmode='transparent' width='425' height='350'></embed>" .                 "</object>";


Changing it to, for example, this:

$code "<object width='{$width}' height='{$height}' data='{$src}' type='application/x-shockwave-flash'>" .
                
"<param name='movie' value='{$src}'></param>" .
                
"<param name='wmode' value='transparent'></param>" .
                
"</object>";


Regards: Colossus



12
colossus
Re: XOOPS 2.3.3 Final Issues
  • 2009/4/12 19:14

  • colossus

  • Just popping in

  • Posts: 43

  • Since: 2007/9/30


Hi:

Quote:
This may be due to cache being used in notifications.php which can be solved by replacing header.php with the one in SVN


Yes, I can confirm that. Header.php SVN version 3066 fixed notifications problem in our site.

Regards: Colossus



13
colossus
Re: Legacy GUI Not working with Microsoft Explorer
  • 2009/4/1 13:51

  • colossus

  • Just popping in

  • Posts: 43

  • Since: 2007/9/30


Hi:

Not much help from here... It's working now, and I cannot duplicate the issue!

Anyway, here is my configuration:

XOOPS - XOOPS 2.3.3
PHP - 5.2.5
MySQL - 4.1.22-standard

Modules:

News 1.61
Protector 3.32
Smartsection 2.13
NewBB 1 (the one in XOOPS 2.0.13.2)
MyDownloads 1.44
MyLinks 1.12
XoopsPool 1.02
Istats 1.01
Comments 1.01

Regards: Colossus



14
colossus
Re: Problem selecting user in Private Message
  • 2009/3/31 20:25

  • colossus

  • Just popping in

  • Posts: 43

  • Since: 2007/9/30


Hi:

I see this bug in XOOPS 2.3.3 also...

Regards: Colossus



15
colossus
Re: Legacy GUI Not working with Microsoft Explorer
  • 2009/3/31 19:38

  • colossus

  • Just popping in

  • Posts: 43

  • Since: 2007/9/30


Hi:

Similar problem here: with IE 6, an updated 2.3.3 site will hang trying to navigate in the admin section with "legacy" theme (issues a blank page, or protector blocks navigation as "crawler").

No problem in Firefox, or in IE with exm theme.

Regards: Colossus



16
colossus
Problem selecting user in Private Message
  • 2009/1/26 12:52

  • colossus

  • Just popping in

  • Posts: 43

  • Since: 2007/9/30


Hi:

In XOOPS 2.3.2b, and maybe prior versions, when you create a new Private Message the list to select recipient user shows only the first 200 entries.

In the file ~/class/xoopsform/formselectuser.php, line 35 states the following:

$limit 200;


Changing this to, say, this...

$limit 1000000;


..solved the problem for us.

Question is if this change may have any effect in other sections of XOOPS engine. As far as I've been able to check, everything else is working fine.

Regards: Colossus



17
colossus
Re: Bug in profile 1.51?
  • 2009/1/7 11:40

  • colossus

  • Just popping in

  • Posts: 43

  • Since: 2007/9/30


Hi:

I've updated our test site 2.3.0 -> 2.3.1 -> 2.3.2b and the bug I reported originally in this threat is still there. I'll explain it again:

Browsing profiles as registered or admin user works OK, but when you see a profile not logged in (anonymously):

1) You get a blank page (debug states "Fatal error: Call to a member function isAdmin() on a non-object in ..../modules/profile/userinfo.php on line 126")

2) If you edit that line as dhsoft recomended in this same threat you get rid of the blank page, but ALL fields in any profile are visible to anonymous users (no matter what you set in Profile's visibility preferences).

Could anyone please address this issue? Are there any plans to update this Profile 1.51, any CVS I can test? This is just stopping us from upgrading to XOOPS 2.3.2b, and I really cannot understand how XOOPS comunity releases a "stable" core version that throws a blank page when upgrading a default installation, and announce proudly that 17,000 users are plagued with this bug.

Thanks in advance, and regards: Colossus

EDIT:I've found that there's a CVN version that fixes this issue, SVN-Profile. Good work, any news on when will it be released?



18
colossus
Re: Bug in profile 1.51?
  • 2008/11/2 10:17

  • colossus

  • Just popping in

  • Posts: 43

  • Since: 2007/9/30


Hi, and thank you for your interest:

Quote:
check User Profile -> Permission - Profile accessible by these groups - Visibility


Yes, permissions are OK. They were working fine in 2.3.0, and I've checked them again after the upgrade... For admin and non-admin users everything is working, but anonymous users can see all profile fields, no matter what I set in visibility confs.

Maybe I should try the upgrade from the beginning again, just to make sure...

Regards: Colossus



19
colossus
Re: Bug in profile 1.51?
  • 2008/11/2 9:53

  • colossus

  • Just popping in

  • Posts: 43

  • Since: 2007/9/30


Hi:

Quote:
as admin you see all fields.


Yes, but as anonymous you shouldn't. And that's what is happening in my test installation.



20
colossus
Re: Bug in profile 1.51?
  • 2008/11/2 9:11

  • colossus

  • Just popping in

  • Posts: 43

  • Since: 2007/9/30


Hi:

Quote:
you can edit the /modules/profile/userinfo.php


That will prevent the error, but will show all fields to the anonymous user...




TopTop
« 1 (2) 3 4 »



Login

Who's Online

242 user(s) are online (160 user(s) are browsing Support Forums)


Members: 0


Guests: 242


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits