1
_masi
xoops.js used to be localized as xoopsjs.php
  • 2004/2/13 12:14

  • _masi

  • Just popping in

  • Posts: 19

  • Since: 2003/3/28


Hi!

Argh, I cannot believe it! Localization degrading instead of improving.

See my bug report including a solution for this severe bug at
Sourceforge.

Masi



2
_masi
no smilies or any other formatting in comments?
  • 2004/2/9 14:53

  • _masi

  • Just popping in

  • Posts: 19

  • Since: 2003/3/28


I used the comments system for one of my own modules. I did that by including comments_view.php.

It seems that the render class CommentsRenderer used by this code ignores the formatting options of the comments.

I have filed a bug on Sourceforge including a bug fix.

Masi



3
_masi
Re: XOOPS and ODBC
  • 2003/7/24 12:42

  • _masi

  • Just popping in

  • Posts: 19

  • Since: 2003/3/28


Try to make brackets around the ON-part of the FROM-clause in the lines 297 and 415 of class/xoopsblocks.php:

$sql .= "FROM ".$db->prefix("newblocks")." b LEFT JOIN ".$db->prefix("group_permission")." l ON (l.gperm_itemid=b.bid) WHERE gperm_name = 'block_read' AND gperm_modid = 1";


$sql 'SELECT b.* FROM '.$db->prefix('block_module_link').' m LEFT JOIN '.$db->prefix('newblocks').' b ON (b.bid=m.block_id) LEFT JOIN '.$db->prefix('group_permission')." l ON (l.gperm_itemid=b.bid) WHERE l.gperm_name = 'block_read' AND gperm_modid = 1";




4
_masi
Re: X2 Core: [code] tag's output correction
  • 2003/6/24 7:01

  • _masi

  • Just popping in

  • Posts: 19

  • Since: 2003/3/28


Andrey, I get multiple lines if i paste your first in example into notepade (using Mozilla and Win98 SE). But I believe you that there are situations where a problem might arise.

My problem with pasting code was that it will be automatically line-wrapped! Argh, I do use long lines with all the indenting and commenting. Your hack/fix also does a line-wrapping at 100.

And if your hacks are really bug fixes, consider submitting them to the Sourceforge bug tracker! Perhaps Ono finds some time and merges your patches.



5
_masi
Re: Autologin for Xoops 2.0.x
  • 2003/6/22 19:43

  • _masi

  • Just popping in

  • Posts: 19

  • Since: 2003/3/28


This hack suffers from the same problem as the original hack in this thread. While it does not expose the login (uname) it exposes the uid and the password.

I'm sure that this feature can be introduced with the 2.0.x branch, though a few config items will have to be added. This will require the admin user to run an update script, of course. But I don't see this as a problem.



6
_masi
Re: Autologin for Xoops 2.0.x
  • 2003/6/21 11:20

  • _masi

  • Just popping in

  • Posts: 19

  • Since: 2003/3/28


Hmm, I'm sure there is way to use a "secret" cookie style without changing the internal stored format (ie plain login and hashed password). I'll try and think of a method - it'd be on paper cause I'm off to a vacation soon.

And you don't need to change many things to get something configurable. XOOPS provides a quite advanced configuration system. It uses a general table and an OO-API for access. I'll dig up some info for you how to use it.



7
_masi
Re: Autologin for Xoops 2.0.x
  • 2003/6/21 8:26

  • _masi

  • Just popping in

  • Posts: 19

  • Since: 2003/3/28


A good start and a fine feature. But I have a few issues.

I don't think it is a good idea to store the actual password in the cookie nor it is to send out a simple hashed version of it. Have a look at sourceforge, they use even a hashed/encrypted login plus a special session_persist cookie.

And of course this feature has to be configurable
A config to turn it on and off and another one to configure the timeout in days.

Anyway I'd love to see this in the official XOOPS.

PS: BTW, I posted an ugly autologin hack myself. It's about an auto-login after an auto-approved registration. Perhaps you could integrate this as well, while you're at it



8
_masi
Re: Smarty version that XOOPS uses
  • 2003/5/21 21:25

  • _masi

  • Just popping in

  • Posts: 19

  • Since: 2003/3/28


Moving them should be fairly easy. I guess it's more or less creating a new dir with the XOOPS Smarty plugins and registering them in the XoopsTpl constructor.

Doing this would also to allow one central installation of Smarty shared by many apps at a site.

I'll investigate this matter.



9
_masi
Smarty version that XOOPS uses
  • 2003/5/21 15:53

  • _masi

  • Just popping in

  • Posts: 19

  • Since: 2003/3/28


As I see it XOOPS uses a vanilla 2.3.0 Smarty.

Only plugins/resource.db.php is new. Is this correct?




TopTop



Login

Who's Online

133 user(s) are online (74 user(s) are browsing Support Forums)


Members: 0


Guests: 133


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