11
mondarse
Planing to start coding my first module, where to start?
  • 2013/6/14 6:00

  • mondarse

  • Just popping in

  • Posts: 96

  • Since: 2003/2/3 1


Hi, I'm planning to start coding my first module for xoops 255, and after reading the forums I'm not sure where to start:

- I have tried TDMCreate 1.39RC1 but generated code simply gets blank page when trying to view new modules to install in my local wampserver (apache 2.2.11, php 5.3, mysql 5.136)

- I have watched "OOP Adventures with XOOPS" presentation.

- I know that irmtfan has done a "How to write an standard module for xoops" manual: https://xoops.org/modules/newbb/viewtopic.php?topic_id=76036, not read yet.

- Should I learn XOOPS API before starting to code, or can I only use it as a reference document?.


So, could you please recommend me where to start?

Thank you, MonDarSE



12
mondarse
Re: upload to server
  • 2013/4/24 10:05

  • mondarse

  • Just popping in

  • Posts: 96

  • Since: 2003/2/3 1


Quote:

chefry wrote:
ok, live and all working without any problems (i hope)

check it out

http://zapenglishclub.com/


Congratulations!!!



13
mondarse
Re: upload to server
  • 2013/4/22 12:52

  • mondarse

  • Just popping in

  • Posts: 96

  • Since: 2003/2/3 1


Quote:

Mamba wrote:

I prefer a fresh installation in a new location, so I don't carry extra baggage from old installations, since over time you collect a lot of un-needed files.

Then I just need to run few tests and copy any "custom" files to the new locations. Moving files is less desired, because once you overwrite a file, you don't have a clear comparison between both installations.


Mamba Maybe I didn't explain my self.
When I say move the old site instead of delete it I mean to put the files in a hidden folder out of web root folder. Something like this:
/httpdocs/(here my old site files)

move them outside root folder:
/old/(here my old site files)

or if you don't have access or permission to that folder something like this:

move all the old file to a new backup folder:
/httpdocs/OLD-backup/(here my old site files)


then as Mamba stated make a fresh clean installation in /httpdocs/





14
mondarse
Re: upload to server
  • 2013/4/22 12:28

  • mondarse

  • Just popping in

  • Posts: 96

  • Since: 2003/2/3 1


When I started my post, Mamba post was not posted already.

Mamba explains it better, and both posts can complement the other.

MonDarSE



15
mondarse
Re: upload to server
  • 2013/4/22 12:24

  • mondarse

  • Just popping in

  • Posts: 96

  • Since: 2003/2/3 1


In my opinion you are ok, I will only do some recommendations based in my experience:

- Backpup your files to you computer and also, if your host provides any kind of cpanel, "move" your old site to other folder instead of deleting it, so if your new installation gets impossible and you finally get frustrated you can get back you old site on-line by moving deleting new installation, moving back your old files and recovering your old db), so you can give "tomorrow" an other chance.
It is easiest to move folder than wait to ftp upload again your old files. Of course you need enough hard disk space for two site at the host.

- Backup your db twice, you never know what could happen.
As you said use phpmyadmin por db, but also try HeidiSQL for win. If have used this software for 3 years and it is very useful. You only need external (internet) db access to mysql databases.

- When installing new 2.5.6. make sure it works every thing before deleting the db and importing the local one.
Check if XOOPS_VAR_PATH if properly configured, try installing some common modules like news, create some stories.

- Test your theme with your 2.5.6. theme before importing your local db. If there are some errors, it is better to find them with less places to look in.

- After all previous check ok, back up your "fresh 2.5.6 db" before delete it and importing your local 2.5.6. db. If it doesn't work, you can easily go back.

- If complete local 2.5.6. db import doesn't work in the webhost to do it step by step:
- Install and check new fresh 2.5.6. (out of the box).
- Do basic configuration / customization.
- Do a db backup
- Install one module, test it, create dummy content and test.
- Import db tables only for the installed module. (Edit the sql file and copy and paste only the required tables to a new file).
- Test the module, and if every thing is ok, import an other module, and repeat previous "sub-steps".
- If you finally get success importing step by step make a db backup.
- Only one more recommendation, when everything online gets working import your 2.5.6. on-line db in your local computer and test it, if it doesn't work locally your webhost and localhost machine configurations are "critically" different, so you must find the differences and try to set config for both the same, so you can make "experiments / install new modules" in your local machine and then upload them to you webhost and meke them run easily.







16
mondarse
Re: D-Transport 2.0.2.2 Beta
  • 2013/2/3 10:58

  • mondarse

  • Just popping in

  • Posts: 96

  • Since: 2003/2/3 1


Only a question, where are the files (the ones the module manage) stored?, in a module's sub-folder or could they be put in a custom folder?

It would be very useful if files are stored in a non public folder (XOOPS_VAR_PATH or something like that) so direct links to files are not possible.

MonDarSE



17
mondarse
Re: Latest Publisher module?
  • 2012/11/27 9:25

  • mondarse

  • Just popping in

  • Posts: 96

  • Since: 2003/2/3 1


Quote:

I'm trying the rc1 in local and I'm having many errors even in the admin side.


I have solved my errors in admin side of Publisher. I have installed it in an a different folder, but I had not used "clone" button at all.

Now, I have done a new clean install in the default folder and everything worked fine, then cloned the module to other folder.

MonDarSE



18
mondarse
Re: Latest Publisher module?
  • 2012/11/27 6:59

  • mondarse

  • Just popping in

  • Posts: 96

  • Since: 2003/2/3 1


Hi Trabis,
please give us the link to the google SVN you are using to make same tests.

I'm trying the rc1 in local and I'm having many errors even in the admin side.

Thanks MonDarSE

edit:Sorry, didn't read previous message from irmtfan. It would be also nice (and better for all) to have access to the module's svn in sf.net



19
mondarse
Re: Possible bug in textsanitizer in xoops 2.5.5 (maybe in previous versions too)
  • 2012/8/24 8:04

  • mondarse

  • Just popping in

  • Posts: 96

  • Since: 2003/2/3 1


As I had no response if I should report the bug to SF, I have searched bug tracker in SF and as I found no report I have done it myself.

Thank you irmtfan again for your quick and useful fix.



20
mondarse
Re: Possible bug in textsanitizer in xoops 2.5.5 (maybe in previous versions too)
  • 2012/8/23 8:00

  • mondarse

  • Just popping in

  • Posts: 96

  • Since: 2003/2/3 1


Thank you very much for your quick solution. I have set 'clickable' => 0, and worked fine.

After your "edit" I don't understand if I should submit a bug in tracker or you have already sent by yourself, or if it can't be considered a bug.

MonDarSE




TopTop
« 1 (2) 3 4 5 »



Login

Username:
Password:

Lost Password? Register now!

Who's Online

74 user(s) are online (50 user(s) are browsing Support Forums)


Members: 0


Guests: 74


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