1
khuhner
Re: Upgrading from 2.0.13.2 to 2.4.4
  • 2011/1/12 3:04

  • khuhner

  • Quite a regular

  • Posts: 232

  • Since: 2006/1/6 3


My ISP has Fantastico which will automatically upgrade my system. Do you recommend using it or should I do the upgrade manually? I dont have a lot of template modifcations so I think it may be OK...thoughts?

Kurt



2
khuhner
Change Email used on Xoops.org?
  • 2011/1/9 1:43

  • khuhner

  • Quite a regular

  • Posts: 232

  • Since: 2006/1/6 3


I've changed my email address but the one I registered with xoops.org is with an email no longer used. Can I change the email that I signed up to the site?

Kurt



3
khuhner
Upgrading from 2.0.13.2 to 2.4.4
  • 2011/1/9 1:37

  • khuhner

  • Quite a regular

  • Posts: 232

  • Since: 2006/1/6 3


It's been a while since I've upgraded as I am on version 2.0.13.2. I'd like to upgrade to 2.4.4. I read the release notes here

https://xoops.org/modules/news/article.php?storyid=5208

Quote:

Upgrading from any XOOPS ranging from 2.0.7 to 2.0.13.2 (using the full package):

0. Unpack the archive to your LOCAL computer (e.g. PC) in a temporary directory.
1. Move the "upgrade" folder inside the "htdocs" folder on your LOCAL computer (it's been kept separate as it's not needed for full installs)
2. Delete htdocs/mainfile.php, htdocs/install/, htdocs/cache/, htdocs/template_c/, htdocs/themes/ and htdocs/uploads/ from the "htdocs" folder on your LOCAL computer
* if you have created XOOPS_TRUST_PATH folder on your server, copy the content of /xoops_lib to that directory, and delete /xoops_lib from the "htdocs" folder on your LOCAL computer
3. Upload the content of the htdocs folder on your LOCAL computer over your existing files on your server
4. Delete the following folders and files from your server (they belong to an old version):
* class/smarty/core
* class/smarty/plugins/resource.db.php
5. Ensure the server can write to mainfile.php (permission 0777 on Linux)
6. If you have Protector previously installed, open the "mainfile.php" file , and remove the Pre-check and Post-check lines (if they exist):

include XOOPS_TRUST_PATH.'/modules/protector/include/precheck.inc.php' ;
include XOOPS_TRUST_PATH.'/modules/protector/include/postcheck.inc.php' ;

7. For security considerations, you are encouraged to move directories xoops_lib (for XOOPS libraries) and xoops_data (for XOOPS data) out of document root, or even change the folder names.
8. Make the directory of xoops_data/ writable; Create and make the directories of xoops_data/caches/, xoops_data/caches/xoops_cache/, xoops_data/caches/smarty_cache/ and xoops_data/caches/smarty_compile/ writable (permission 0777 on Linux).
9. Access /upgrade/ with a browser, and follow the instructions
10. Write-protect mainfile.php again (permission 0444 on Linux)
11. Delete the "upgrade" folder from your server
12. Update the "system" module from the modules administration interface, other modules are recommended to update as well


If I am reading this right I can upgrade from 2.0.13.2 to 2.4.4 with one single upgrade? Or do I need to do an intermediate upgrade, then another upgrade to 2.4.4?

Kurt



4
khuhner
Re: Module Repository: Question and Answer Session
  • 2009/6/19 18:33

  • khuhner

  • Quite a regular

  • Posts: 232

  • Since: 2006/1/6 3


Quote:

redheadedrod wrote:
Along with the incorporation of module hooks I have been dreaming up a new way of doing the modules as well.


I also agree that XOOPS should look at an effective module development framework, whether it is a hook or framework. I would suggest something along the lines of the Model-Controller-View paradigm (ala NextStep, OpenStep). I developed client/server code in C and Objective-C for years, yet I find creating modules in XOOPS to be complicated, even with my experience. It should be easy, edit a few files, etc.

Xoops could distinguish itself by offering such a tool.

In regards to some other comments, I hated to look for modules on several sites (xoops.org, module developers, hacks of the module). Why cant all the module developers utlilze SF or some other commen single location?

Kurt



5
khuhner
Re: "Last login" not updated?
  • 2007/10/1 17:23

  • khuhner

  • Quite a regular

  • Posts: 232

  • Since: 2006/1/6 3


, ,



6
khuhner
Re: How can I build a new module?
  • 2007/9/8 0:08

  • khuhner

  • Quite a regular

  • Posts: 232

  • Since: 2006/1/6 3


Quote:

Cozzie wrote:
2 wrap the current search scripts into a XOOPS module.


For #2 use a module like MyiFrame or a general content module like CJayContent and wrap the link using