Hi

You have set the articles module as start module and there are no articles to display, so the article module redirects you to the XOOPS root url which redirects you to the articles module....

Type http://your_xoops_url/admin.php and change the start module under System >> General Settings

greetings
birdseed

Hi
This is how to add a custom block

Let's say that XXX is the module you want to add a block to.

1. Go to modules/XXX/templates/blocks and create a myblock.html with the following content:

<{$block.mycontent}>

go to modules/XXX/blocks and add a myblock.php with the following content:

function myblock_show($options)
{
$block = array();
$block['mycontent'] = 'This is my content';
return $block;
}

function myblock_edit($options)
{
return "Here I could write my own block editor";
}
?>

3. Add the following entry to modules/XXX/xoops_version.php

$modversion['blocks'][] = array(
'file' => "myblock.php",
'show_func' => "myblock_show",
'edit_func' =>"myblock_edit",
'options' => '',
'name' => 'Hello Block!',
'description' => 'This jenny from the block',
'template' => 'myblock.html');

Have fun!

greetings
birdseedmusic

Hi

*push*

hoping for answers... ;)

greetings
birdseedmusic

Hi

xoops uses a SQL LIKE '%foobar%' Syntax to do fulltext seach on forum posts, comments, news...

This takes quite a lot of performance. You can even start a DOS Attack by simply doing a lot of searching in a short period.

There is a mySQL FULLTEXT search index which should solve this problem. You also have to rewrite the queries. Is there any reason why XOOPS still uses the slow LIKE criteria? Is there a hack available?

greetings
birdseedmusic

Hi

I also fully agree with this. My 20000 Members community, online since 2002, has never been hacked by using the loginname an guessing the password.

greetings
birdseedmusic

Hi

Definitely more difficult than getting this module for xoops2 running.

greetings
mk

Hi

Yes i own an old Vespa 50N Special...same thing. ;)

Sorry I can´t spend much time on this. phpmychat ain´t really worth it. the code is too ugly to perform any further development.

if you could post any meaningful error message or something?

greetings
birdseedmusic

Hi pmhoran

I never tested phpmychat for xoops2 but i don´t think it should be a problem. just try it.

I remember that the chat needs some tables:

CREATE TABLE `XOOPS_c_ban_users` (
`username` varchar(30) NOT NULL default '',
`latin1` tinyint(1) NOT NULL default '0',
`ip` varchar(16) NOT NULL default '',
`rooms` varchar(100) NOT NULL default '',
`ban_until` int(11) NOT NULL default '0'
) TYPE=MyISAM;

-- --------------------------------------------------------

--
-- Tabellenstruktur für Tabelle `XOOPS_c_messages`
--

CREATE TABLE `XOOPS_c_messages` (
`type` tinyint(1) NOT NULL default '0',
`room` varchar(30) NOT NULL default '',
`username` varchar(30) NOT NULL default '',
`latin1` tinyint(1) NOT NULL default '0',
`m_time` int(11) NOT NULL default '0',
`address` varchar(30) NOT NULL default '',
`message` text NOT NULL
) TYPE=MyISAM;

-- --------------------------------------------------------

--
-- Tabellenstruktur für Tabelle `XOOPS_c_reg_users`
--

CREATE TABLE `XOOPS_c_reg_users` (
`username` varchar(30) NOT NULL default '',
`latin1` tinyint(1) NOT NULL default '0',
`password` varchar(32) NOT NULL default '',
`firstname` varchar(64) NOT NULL default '',
`lastname` varchar(64) NOT NULL default '',
`country` varchar(64) NOT NULL default '',
`website` varchar(64) NOT NULL default '',
`email` varchar(64) NOT NULL default '',
`showemail` tinyint(1) NOT NULL default '0',
`perms` varchar(9) NOT NULL default '',
`rooms` varchar(128) NOT NULL default '',
`reg_time` int(11) NOT NULL default '0',
`ip` varchar(16) NOT NULL default '',
`gender` tinyint(1) NOT NULL default '0'
) TYPE=MyISAM;

-- --------------------------------------------------------

--
-- Tabellenstruktur für Tabelle `XOOPS_c_users`
--

CREATE TABLE `XOOPS_c_users` (
`room` varchar(30) NOT NULL default '',
`username` varchar(30) NOT NULL default '',
`latin1` tinyint(1) NOT NULL default '0',
`u_time` int(11) NOT NULL default '0',
`status` char(1) NOT NULL default '',
`ip` varchar(16) NOT NULL default '',
UNIQUE KEY `room` (`room`,`username`)
) TYPE=MyISAM;


just replace te XOOPS_ with your own prefix.

about the other chat...i´ve contacted the dev ans suggested him to release a beta version.

greetings
birdseedmusic

Hi

This is your lucky day:

http://homerecording.de/birdseed/chat.zip

phpmychat as a module....

but...

for xoops1 :(

greetings
birdseedmusic

ps.
We have a template-based xoops2 chat now. he event works under xoops2.2 but there are some dirty hacks wich need to be removed. There are some german words hardcoded. our chat programmer wants to refactor it for XOOPS 2.2 with oop and everything. but he has much to do so this can take some time.

Hi

@mcnaz
Okay, let´s discuss it ;)
I think we both know the difference between compiled and interpreted language, about MSIL and Bytecode, JIT and stuff. So let´s not get stuck in that discussion.
In php, you don´t have a compiler who says: in line 123, there is a datatype conversion error. in line 456, the called function is not declared. we both know.

I have written a module named webmusic, which uses a class named Category. Now it is named WebmusicCategory, because yesterday *bang* a naming conflict with a class Category in CBB occured. Such things happen if there is no compiler (okay, you could solve it with namespaces, but I nevertheless, I hope you see the point -> runtime errors instead of compile-time errors)

okay so if homerecording.de gets the double size:
When I speak of mssql, i don´t focus on speed, i mean foreign key constraints, stored procedures, triggers, transactions. Everything to guarantee data integrity in a complex environment. my page ain´t that complex that i would need such things. and MySQL is okay ans stable, with 4.1 we will be able to change for example uids in a simple way with the help of foreign key constraints, this is a big step ahead for us because we need that for merging to platforms together. okay, but it i had a even bigger and more complex site, i should have the money to host a webgarden or webfarm . as this is not the fact at the moment, I hope to gain some performance in the core hacks I´m planning now.

But generally, I see some boundaries in the complexity of php(mysql applications. I see the typical XOOPS problem, that with every hack, there is a new problem anywhere else.

So I am afraid, that someday, we have a xoosphere that is so complex that you need weeks to find a simple bug, because in line 1234, the serializer made a wrong unicode conversion. So a week later, a user complains about a smilie not showing correctly.

And I am afraid that it will make XOOPS slower. We will have more queries, we will have a load of class includes which need to be parsed. As in php, with every request objects need to be newly created (or did I miss a new application cache in php5?), this could be time-consuming. You could use serialisation to make this faster, but this could lead to new problems, or you need more code to validate the deserialisation process.

I hope I am just a stupid sceptic who hasn´t understood the concept. But at the moment, i am a bit pessimistic about xoosphere.

@phpbbb

I have sent you the class.forumpost.php. It is rather a dirty hack which writes the sanitized text to an extra column in the newbb_posts_text table. so at every display, XOOPS doesn´t have to do the sanitizing process again.

greetings
birdseedmusic