293191
Hapko3
Re: remembering logins?
  • 2003/4/28 22:44

  • Hapko3

  • Just popping in

  • Posts: 2

  • Since: 2003/4/1 1


ttt



293192
onokazu
Re: XoopsGallery comments error
  • 2003/4/28 16:56

  • onokazu

  • XOOPS Founder

  • Posts: 617

  • Since: 2001/12/13


This has been fixed on CVS. You can download the fixed file here.



293193
ryana
Re: PostNuke to XOOPS conversion
  • 2003/4/28 11:59

  • ryana

  • Just popping in

  • Posts: 3

  • Since: 2003/2/9 6


This function Quote:
// Do the users table - exclude any user that would overwrite XOOPS admin's
function BuildUserTable() {
global $fromdb, $todb;
//$altertable="ALTER TABLE `boardjive_users` CHANGE `pn_user_regdate` `pn_user_regdate` TIMESTAMP";
//$result = mysql_query($altertable);
$sql = "INSERT INTO ".$todb.".xoops_users (uid, name, uname, email, url, user_avatar, user_regdate, user_icq, user_from, user_sig, user_viewemail, user_aim, user_yim, user_msnm, pass, user_intrest, user_occ)
SELECT pn_uid, pn_name, pn_uname, pn_email, pn_url, pn_user_avatar, UNIX_TIMESTAMP(NOW()) as pn_user_regdate, pn_user_icq, pn_user_from, pn_user_sig, pn_user_viewemail, pn_user_aim, pn_user_yim, pn_user_msnm, pn_pass, pn_user_intrest, pn_user_occ
FROM ".$fromdb.".boardjive_users";
// WHERE ".$fromdb.".pn_users.uid <> '110'";
$delete=True;
$tbname=$todb.".xoops_users";
DoTable($delete, $sql, $tbname);
//echo $sql;
}


...would seems to indicate that inserting postnuke.pn_pass into xoops.pass will work without any problems. That's what I needed to know. Thanks!



293194
chapi
Re: PostNuke to XOOPS conversion
  • 2003/4/28 11:17

  • chapi

  • Theme Designer

  • Posts: 611

  • Since: 2002/1/22


You can download the Conversion Template from Boobtoob here:

https://xoops.org/modules/mydownloads/singlefile.php?lid=204

This was built for converting data from Postnuke 7.1x to XOOPS 3.0x. But maybe it is a good starting point for you.



293195
ryana
PostNuke to XOOPS conversion
  • 2003/4/28 10:58

  • ryana

  • Just popping in

  • Posts: 3

  • Since: 2003/2/9 6


Yes, I know this question was asked before. The information link given, however, is dead. There are two questions that I have:

1) Through searching I have seen that a PostNuke to XOOPS script would be provided in the full release. Since XOOPS is now at v2.0.2 (stable) it must be a full release. I do not see a conversion script in the package. Am I missing something?

2) If there are no conversion scripts, the only thing that would give me a problem is use passwords. Does PN & XOOPS encrypt the passwords in the same manner? If I simply import the PN user passwords into the XOOPS password field, would they work?



293196
El_Jordo
IP Addresses in Forums
  • 2003/4/27 20:03

  • El_Jordo

  • Just popping in

  • Posts: 64

  • Since: 2003/4/23


Is there a way for administrators to track IP addresses in the standard XOOPS forum module? It must be there, since IPs appear in Comments. But I've looked and can't find it in the forums. Thanks!



293197
TitaNs
Re: Database problem
  • 2003/4/26 18:18

  • TitaNs

  • Just popping in

  • Posts: 7

  • Since: 2003/4/11


2. Create a database user that XOOPS will use
3. Give access to log in to the database user
4. Create a database instance that XOOPS will use


I dunno how to set database what XOOPS want?
can someone tell me the settings of xoop database?..



293198
gstarrett
Re: XoopsGallery comments error
  • 2003/4/25 19:23

  • gstarrett

  • Friend of XOOPS

  • Posts: 174

  • Since: 2002/3/12


Bump. Anyone? Should I direct this toward anyone in particular? I looked through the wiki but it didn't help (maybe I just didn't see the correct secion?).



293199
gstarrett
XoopsGallery comments error
  • 2003/4/25 4:00

  • gstarrett

  • Friend of XOOPS

  • Posts: 174

  • Since: 2002/3/12


Hi all--I'm still working on understanding all the ins & outs of the new XOOPS + Smarty + XoopsGallery and was hoping someone could point me in the right direction.

When I add a comment, and look at the /include/comment_form.php (included by /modules/XoopsGallery/comment_new.php) hidden inputs, the "extra_param" values are blank. I think I MAY have found the source of the problem. in /include/comment_form.php line 109 says:
Quote:
$hidden_value = isset(${$extra_param}) ? htmlspecialchars(${$extra_param}, ENT_QUOTES) : '';


...and it is NOT including the values. However, when I change register_globals to ON, it works. Should I correct the above line, or is it the responsibility of the /modules/XoopsGallery/comment_new.php to set them in the first place? I looked for a generic "HTTP_GET|POST_VARS to Local vars" routine, but didn't find any one place--it looks like the modules are responsible for the pulling in, but I'm not sure.

Where does the patch need to go? XOOPS core or XoopsGallery? I've seen other posts about "some modules don't work correctly yet with register_globals off", could this be why??

I am just starting to dip my toe into the new Xoops2 setup, but it looks very nice so far (albeit a bit of a learning curve--I've only started OO programming and am very new to it in PHP and it's a little "spread out"). Any help is appreciated.

Regards,

Glen Starrett



293200
Rooster
Re: HTML problem in XOOPS and Other CMS?
  • 2003/4/24 15:17

  • Rooster

  • Just popping in

  • Posts: 32

  • Since: 2003/4/1 1


Quote:
danyblue wrote:
I am trying to map pages made in HTML inside the Section and news part of XOOPS. i just have a problem that i don't know how to solve. XOOPS insert in the beginning of all the content a lot of empty space, which makes my content go down in the window and not being seen right from the beginning. Does any one know how to solve this problem?

If anyone is using tables in the CMS content engine, you need to do two things to solve this problem. First, eliminate all "#" characters in your table. Why? Because it's a character that is used to "comment" text, and, for some reason, is read in the PHP scripting when the page is loaded in a Unix environment. All table tags that lay between two "#" characters are not read in your table, and therefore, your table structure collapses like a house built with a deck of cards. Use common names for your cell colors (Websafe), if you are using bg and font colors.

Second, there can be no spaces or line breaks in the table — well, maybe, one. See if it helps by not having any line breaks in your table. You can see an example of this use in an article about XOOPS here:

Example of Table in Sections

I had the same problem before discovering a solution.







Login

Who's Online

711 user(s) are online (462 user(s) are browsing Support Forums)


Members: 0


Guests: 711


more...

Donat-O-Meter

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

Latest GitHub Commits