292381
Wally
Dynamic menu
  • 2003/7/25 6:50

  • Wally

  • Just popping in

  • Posts: 4

  • Since: 2003/7/3 1


I installed a Dynamic menu (like in e-xoops) for XOOPS 1.3
Got question:
Is it possible to specialize this menu ONLY on MY DOWNLOADS module, not on whole site?
If yes, what should I change in script?

Thx!



292382
DobePhat
Re: Autologin - does it update xoopsmembers "last login date"
  • 2003/7/25 3:42

  • DobePhat

  • Friend of XOOPS

  • Posts: 656

  • Since: 2003/4/15


This is very promising, but what about "whos online" will that still work Or will they forever be online? Also can someone please direct me to the most recent hack we were talking about...I uh sort of got lost in this thread and now I have a bunch of downloads that Im not sure about...



292383
sunsnapper
Re: Don't forget about the accesibility

Quote:
This is one area where I would think that the ability for users to choose and keep their own theme was a benefit.

Accesibility could be tailored directly to the users needs.

Be there needs as in the above post, or if users are using different browsers, or say some prefer a "light" look or a "more featured" look. Flash or non-flash, different screen resoloutions and so on,

Shame imo no longer available as it does offer many more options to xoops. And opens more doors to users to use the site.


I think you can try the "Theme" Block:
System Admin | Blocks | Theme

I'm pretty sure it is an interface to allow users to choose a theme.

Perhaps it could be extended to read a cookie or an entry in the user DB to remember the chosen theme?

I know Ackbarr is using it, if you want to see a demo:
http://ackbarr.greatweb.com/



292384
mvandam
Re: Don't forget about the accesibility
  • 2003/7/24 20:08

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


Olorin and mike--h,

Very good points. I agree completely about making sites accessible; not only to people with disabilities, but also to people with older browsers or with browser features (e.g. javascript) turned off. And I agree that XOOPS news a little work with respect to the last one.

As for user-selected themes, it had never occurred to me that choosing themes might be for *accessiblity* reasons. Ideally CSS is supposed to solve such problems allowing a website to rely on browser default settings for font-size, etc... and to allow the webpage to be rendered on WAP devices or voice devices. In practice that is a huge amount of bother, people don't know how to do it, and even if they did, many browsers don't support complex CSS (layout, etc.) very well. Until we get to that point, maybe user-selected themes are a good intermediate.

Definitely some food for thought.



292385
nhallman
Headlines Block Disappears
  • 2003/7/24 18:35

  • nhallman

  • Just popping in

  • Posts: 4

  • Since: 2002/12/12


XOOPS 2.0.2, module "xoopsheadline":

My headlines block was here a few hours ago, now it's gone. No changes were made that should have affected this.

The block is set to "visible" in "top page." (It's set to display at top right) All users and groups have rights to access the Headlines module as well as the Headlines block.

The news site I'm trying to display in the headlines block is set up correctly, "Display in Block" is checked and cache time is 1 hour. /cache has 777 permissions.

The URL for the XML/RSS file is valid.

All this have I checked, but it's as if the block doesn't even exist!! What am I overlooking?

Thanks,

Nick



292386
nhallman
Re: time to say goodbye to newbb?
  • 2003/7/24 18:29

  • nhallman

  • Just popping in

  • Posts: 4

  • Since: 2002/12/12


Quote:

destrux wrote:
nhallman, if you would like more developers to possibly contribute to your LMS modules please check the xmode team site


Thanks, I'll check it out...



292387
_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";




292388
frank_lin
Re: XOOPS and ODBC
  • 2003/7/24 12:29

  • frank_lin

  • Just popping in

  • Posts: 2

  • Since: 2002/10/18


hi,
(1)installed odbc layer, modified mainfile.php
(2)export MySQL tables into Microsoft Access 2000( xoops.mdb)
(3)created data source name xoops_access
(4)http://XXXX/xoops, i got a lot of error messages..

any body can help me!
Thanks
best regards
frank

Notice: Undefined offset: 0 in C:\Inetpub\wwwroot\twxoops203_20030626\html\kernel\session.php on line 102

Notice: Undefined variable: rs_assoc in C:\Inetpub\wwwroot\twxoops203_20030626\html\class\database\odbc\db.php on line 127

Warning: SQL error: [Microsoft][ODBC Microsoft Access driver ] query expression 'b.bid=m.block_id LEFT JOIN xoops_group_permission l ON l.gperm_itemid=b.bid' systax error (no operand)。, SQL state 37000 in SQLExecDirect in C:\Inetpub\wwwroot\twxoops203_20030626\html\class\database\odbc\db.php on line 232

Warning: odbc_fetch_into(): supplied argument is not a valid ODBC result resource in C:\Inetpub\wwwroot\twxoops203_20030626\html\class\database\odbc\db.php on line 121

Warning: Invalid argument supplied for foreach() in C:\Inetpub\wwwroot\twxoops203_20030626\html\class\database\odbc\db.php on line 123

Notice: Undefined variable: rs_assoc in C:\Inetpub\wwwroot\twxoops203_20030626\html\class\database\odbc\db.php on line 127



292389
Catzwolf
Re: htmlArea - WYSIWYG editor
  • 2003/7/24 0:28

  • Catzwolf

  • Home away from home

  • Posts: 1392

  • Since: 2007/9/30


My suggestion would be only to give webmaster access to WYSIWYG editors. There is to much of a risk in giving 'users' this option.

But in saying that I have been asked many times to allows 'users' (submit) access to the WYSIWYG editor within WF and I have refused.

But if they where, limits could be impossed via $myts as it was in XOOPS version 1 with 'allowed HTML' (which personally I would like to see back again) and that way Admin could control what HTML tags would be passed and allowed.

Just my one pence worth!



292390
mvandam
Re: htmlArea - WYSIWYG editor
  • 2003/7/24 0:25

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


Thanks for the reply. It looks possible to modify htmlarea to disable 'code-mode' for certain users and/or to remove certain types of html elements from the htmlarea "menu".

On second thought, this is not where the *real* security happens though. The real security needs to happen on the backend. (Otherwise someone can just "forge" a form and submit to your XOOPS site a piece of text containing any tags he/she wishes). So the backend is where the tag restrictions etc. must happen.

It would be nice for the site visitors if the front-end (i.e. htmlarea) matched the acceptable set of tags though.

Seems like a reasonably big job though entirely possible. If XOOPS does eventually adopt something like this, the *first* step is securing the back end possibly allowing non-admins to enter a limited set of tags. The next step would be adding the HTML area.

Remember also, not everyone likes HTMLareas. I much prefer editing in text mode (or code mode), and would prefer to see a textarea even if an htmlarea was supported. I'm sure there are at least a few others who would agree. Perhaps that could be a user preference.







Login

Who's Online

257 user(s) are online (179 user(s) are browsing Support Forums)


Members: 0


Guests: 257


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