102
Only problem with Smartprofile is it doesn't have additional fields, i thought....formulize does yet with loads of extra bits needed....
David's right, yet really we want to build the support of additional fields into XOOPS soon anyway...
Sorry Mike, this makes it sound even more complicated, when it shouldn't have to be....
David's right, yet really we want to build the support of additional fields into XOOPS soon anyway...
Sorry Mike, this makes it sound even more complicated, when it shouldn't have to be....
107
Allot of the Article systems have wysiwyg (What You See Is What You Get) editors built in and XOOPS has its own image manager.....yet you can also drag online images into a wysiwyg editor from a folder also....
108
Who is working on fixing the module dev right now?
As really if we are going to make it what we need as a few of us have been discussing via IM………. Then it needs making into a full module repository and fixing centre in one go…it doesn’t need to be as it was before, yet refined loads to make it much better:::
1) A full repository for all our modules (hosting files on the server that the Foundation owns for us) + maybe using Sourceforge as backup to clean up the system and keep all items in one place.
2) Much more functional error reporting system and commenting for us to use on development and discussions for improvement (releases on the News can then be for glory and not as an error reporting system).
3) Clean and easier management system as to act as a full repository (each item from this point can have a description like before, yet more interactive where items get fixed and bugs and patches are easily submitted……. and not when you ask, you are told to wait and find the original author….fixes are there to improve user functionality for all and sometimes module authors are no longer around to ask.
4) Clear and informative up to date manual and development guidelines for incorporation of modules into the XOOPS system…now though this could be on a XOOPS Wiki, it needs direct linking in one place (so people can post and then edit code for improvements before acceptance into either module or core).
5) SVN copy of modules built in as to see latest development and fixes implemented into a working module, which can then be downloaded directly by any user.
Anyways loads more on this wish list, yet if we aim this way rather then backwards anymore, then perhaps we might get some work done around here….
As really if we are going to make it what we need as a few of us have been discussing via IM………. Then it needs making into a full module repository and fixing centre in one go…it doesn’t need to be as it was before, yet refined loads to make it much better:::
1) A full repository for all our modules (hosting files on the server that the Foundation owns for us) + maybe using Sourceforge as backup to clean up the system and keep all items in one place.
2) Much more functional error reporting system and commenting for us to use on development and discussions for improvement (releases on the News can then be for glory and not as an error reporting system).
3) Clean and easier management system as to act as a full repository (each item from this point can have a description like before, yet more interactive where items get fixed and bugs and patches are easily submitted……. and not when you ask, you are told to wait and find the original author….fixes are there to improve user functionality for all and sometimes module authors are no longer around to ask.
4) Clear and informative up to date manual and development guidelines for incorporation of modules into the XOOPS system…now though this could be on a XOOPS Wiki, it needs direct linking in one place (so people can post and then edit code for improvements before acceptance into either module or core).
5) SVN copy of modules built in as to see latest development and fixes implemented into a working module, which can then be downloaded directly by any user.
Anyways loads more on this wish list, yet if we aim this way rather then backwards anymore, then perhaps we might get some work done around here….
109
+1
Trying to build bridges via IM and communication with everyone and seeing if we can get the one thing back, that made me choose XOOPS to begin with, community!....
Trying to build bridges via IM and communication with everyone and seeing if we can get the one thing back, that made me choose XOOPS to begin with, community!
....
110
Quote:xoops_version.php?
Will_H wrote:
yeah, I would probabaly start with the imenu module.
You do not have to delete them. Just rename the Xoopsinfo.php to like 1xoopsinfo.php.
Do that one by one until the module list reappears.
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | May 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|