11
unni82
Extcal events error
  • 2006/2/26 9:03

  • unni82

  • Just popping in

  • Posts: 35

  • Since: 2005/11/10


hi
i m using XOOPS 2.0.13.1 and installed 'eXtCal for XOOPS 2.0.13.1' module but it doesnt show events i have registered in the calender but in 2.0.13.2 its working fine.what to do somebody give me an answer



12
unni82
news
  • 2006/2/21 10:23

  • unni82

  • Just popping in

  • Posts: 35

  • Since: 2005/11/10


i m using news module with attach option and i m directly attaching this.and while i upload image its thumbnail is not coming properly as with incorrect path. is there any pblm with this module .is there any option to include documents also like doc or ppt as now with images



13
unni82
Re: Image topic error on show
  • 2006/2/21 10:21

  • unni82

  • Just popping in

  • Posts: 35

  • Since: 2005/11/10


Me also similar problem in news the image is showing but with error as the path not correct. i have already asked this and was no reply.and also iwould like to add other files like .doc,.ppt etc so how to do the change



14
unni82
new applicaion in news module
  • 2006/2/16 6:33

  • unni82

  • Just popping in

  • Posts: 35

  • Since: 2005/11/10


hi
i m using news module with attachments and i cant attach msword or other applications .Only jpg,mpeg.... r allowed.so is there any hack i can do inorder to attach this word and other documents.
another prob is that when i attach documents and when it is displayed there s some thumbnail but without any icon and that 'x' symbol without proper path. when clicked it goes to that picture.dont know whats this .
pls help!*



15
unni82
xoops upgrade
  • 2006/2/15 14:09

  • unni82

  • Just popping in

  • Posts: 35

  • Since: 2005/11/10


hi
currently i m running a XOOPS site and my version is 2.0.13 and i want to upgrade it to XOOPS 2.2.3 and i have already installed some 10-12 modules in the current version so if i update it to newer version will these modules work and what upgrade patch should i use for upgrading frm 2.0.13 to 2.2.3?



16
unni82
modules
  • 2006/2/9 8:37

  • unni82

  • Just popping in

  • Posts: 35

  • Since: 2005/11/10


hi
if i m upgrading my XOOPS version 2.0.13 to 2.2.3 will the modules and all the data that i created in 2.0.13 lost?i have installed certain modules and customised it will it all be lost?then what r the precautions to be taken if i m upgrading



17
unni82
Re: Module cloning
  • 2006/2/8 5:05

  • unni82

  • Just popping in

  • Posts: 35

  • Since: 2005/11/10


Quote:

unni82 wrote:in ur case i dont know which module u r using but i think function names r recurring so u need to check in functions.php for recurring functions in the same modules and change the function name which should reflect in all the coming files
hi
i m saying on behalf of module pical .it varies according to modules

1. First Copy the entire folder named “pical” from the server [ .. /.. /modules/pical ] into your Local machine.


2. In the file xoops_version.php (can be found inside the pical folder) change the value of the ' dirname':
$modversion['dirname ' ] = "pical2";

3. Seek and replace in all the files the references to the repertory, ie:
“/modules/pical/” by “/modules/pical2/”

4. In the file xoops_version.php modify the references to the table: $modversion['tables'][0] = 'pical2_event';
Seek and replace in all the files the references to the table. In this case, make research several times: with simple and doubles quotes, with and without spaces:
Replace prefix (' pical '), prefix ("pical"), prefix (' pical') ... by prefix (' pical2 ')

5. Certain modules have a file include\read_config.php (or equivalent). Then all the above mentioned changes need to be made in that file as well.

6. In the file xoops_version.php only modify the noun of the function
$$modversion['search']['func ' ] = "pical2_search";
Publish the file include\search.inc.php and modify the noun of the function
function pical2_search($queryarray, $$andor, $$limit, $$offset, $$userid)

7. In the file xoops_version.php modify the noun of the functions approve and update:
$$modversion['comments']['callbackFile ' ] = ' include/comment_functions.php ';
$$modversion['comments']['callback']['approve ' ] = ' pical2_com_approve ';
$$modversion['comments']['callback']['update ' ] = ' pical2_com_update ';

8. In the file xoops_version.php modify the noun of the function look_up:
$$modversion['notification']['lookup_func ' ] = ' news02_notify_iteminfo ';

9.This step is nonessential, but preferable. Change the names of the files in xoops_version.php, without forgetting to re-elect correctly those in the repertory templates
$$modversion['templates'][1]['file ' ] = "pical2_archive.html";

10. To modify the logo and make it available in the administration of the modules.
Once modified, think of re-electing it and of changing the name indicated in xoops_version.php.
$$modversion['image ' ] = "images/pical2_slogo.png";

11. Go to the administration menu of the modules: your clone should appear without any error messages. Install your clone. Launch your clone. Test all the configurations of blocks and functionalities (research, comments, notification).



These tests must be carried out in the 2 cases of figure:
- With the original version installed, to detect conflicts or interactions
- Without the original version installed (temporarily removed) to check that your clone is autonomous, and that certain files do not point to the original module.



18
unni82
Re: Module cloning
  • 2006/2/8 5:05

  • unni82

  • Just popping in

  • Posts: 35

  • Since: 2005/11/10


Quote:

unni82 wrote:in ur case i dont know which module u r using but i think function names r recurring so u need to check in functions.php for recurring functions in the same modules and change the function name which should reflect in all the coming files
hi
i m saying on behalf of module pical .it varies according to modules

1. First Copy the entire folder named “pical” from the server [ .. /.. /modules/pical ] into your Local machine.


2. In the file xoops_version.php (can be found inside the pical folder) change the value of the ' dirname':
$modversion['dirname ' ] = "pical2";

3. Seek and replace in all the files the references to the repertory, ie:
“/modules/pical/” by “/modules/pical2/”

4. In the file xoops_version.php modify the references to the table: $modversion['tables'][0] = 'pical2_event';
Seek and replace in all the files the references to the table. In this case, make research several times: with simple and doubles quotes, with and without spaces:
Replace prefix (' pical '), prefix ("pical"), prefix (' pical') ... by prefix (' pical2 ')

5. Certain modules have a file include\read_config.php (or equivalent). Then all the above mentioned changes need to be made in that file as well.

6. In the file xoops_version.php only modify the noun of the function
$$modversion['search']['func ' ] = "pical2_search";
Publish the file include\search.inc.php and modify the noun of the function
function pical2_search($queryarray, $$andor, $$limit, $$offset, $$userid)

7. In the file xoops_version.php modify the noun of the functions approve and update:
$$modversion['comments']['callbackFile ' ] = ' include/comment_functions.php ';
$$modversion['comments']['callback']['approve ' ] = ' pical2_com_approve ';
$$modversion['comments']['callback']['update ' ] = ' pical2_com_update ';

8. In the file xoops_version.php modify the noun of the function look_up:
$$modversion['notification']['lookup_func ' ] = ' news02_notify_iteminfo ';

9.This step is nonessential, but preferable. Change the names of the files in xoops_version.php, without forgetting to re-elect correctly those in the repertory templates
$$modversion['templates'][1]['file ' ] = "pical2_archive.html";

10. To modify the logo and make it available in the administration of the modules.
Once modified, think of re-electing it and of changing the name indicated in xoops_version.php.
$$modversion['image ' ] = "images/pical2_slogo.png";

11. Go to the administration menu of the modules: your clone should appear without any error messages. Install your clone. Launch your clone. Test all the configurations of blocks and functionalities (research, comments, notification).



These tests must be carried out in the 2 cases of figure:
- With the original version installed, to detect conflicts or interactions
- Without the original version installed (temporarily removed) to check that your clone is autonomous, and that certain files do not point to the original module.



19
unni82
Re: Module cloning
  • 2006/2/8 4:53

  • unni82

  • Just popping in

  • Posts: 35

  • Since: 2005/11/10


hi
i m saying on behalf of module pical .it varies according to modules

1. First Copy the entire folder named “pical” from the server [ .. /.. /modules/pical ] into your Local machine.


2. In the file xoops_version.php (can be found inside the pical folder) change the value of the ' dirname':
$modversion['dirname ' ] = "pical2";

3. Seek and replace in all the files the references to the repertory, ie:
“/modules/pical/” by “/modules/pical2/”

4. In the file xoops_version.php modify the references to the table: $modversion['tables'][0] = 'pical2_event';
Seek and replace in all the files the references to the table. In this case, make research several times: with simple and doubles quotes, with and without spaces:
Replace prefix (' pical '), prefix ("pical"), prefix (' pical') ... by prefix (' pical2 ')

5. Certain modules have a file include\read_config.php (or equivalent). Then all the above mentioned changes need to be made in that file as well.

6. In the file xoops_version.php only modify the noun of the function
$$modversion['search']['func ' ] = "pical2_search";
Publish the file include\search.inc.php and modify the noun of the function
function pical2_search($queryarray, $$andor, $$limit, $$offset, $$userid)

7. In the file xoops_version.php modify the noun of the functions approve and update:
$$modversion['comments']['callbackFile ' ] = ' include/comment_functions.php ';
$$modversion['comments']['callback']['approve ' ] = ' pical2_com_approve ';
$$modversion['comments']['callback']['update ' ] = ' pical2_com_update ';

8. In the file xoops_version.php modify the noun of the function look_up:
$$modversion['notification']['lookup_func ' ] = ' news02_notify_iteminfo ';

9.This step is nonessential, but preferable. Change the names of the files in xoops_version.php, without forgetting to re-elect correctly those in the repertory templates
$$modversion['templates'][1]['file ' ] = "pical2_archive.html";

10. To modify the logo and make it available in the administration of the modules.
Once modified, think of re-electing it and of changing the name indicated in xoops_version.php.
$$modversion['image ' ] = "images/pical2_slogo.png";

11. Go to the administration menu of the modules: your clone should appear without any error messages. Install your clone. Launch your clone. Test all the configurations of blocks and functionalities (research, comments, notification).



These tests must be carried out in the 2 cases of figure:
- With the original version installed, to detect conflicts or interactions
- Without the original version installed (temporarily removed) to check that your clone is autonomous, and that certain files do not point to the original module.



20
unni82
Re: upgradation to 2.2
  • 2006/2/8 4:42

  • unni82

  • Just popping in

  • Posts: 35

  • Since: 2005/11/10


hi
is it possible to use active directory authentication system in XOOPS 2.0 or 2.2 .i seen one hack in the link but it seems hard to install

https://sourceforge.net/tracker/index.php?func=detail&aid=1320898&group_id=41586&atid=430842

dont know anybody know abt this pls comment




TopTop
« 1 (2) 3 4 »



Login

Who's Online

144 user(s) are online (83 user(s) are browsing Support Forums)


Members: 0


Guests: 144


more...

Donat-O-Meter

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

Latest GitHub Commits