21
mvandam
Re: Don´t allow editing the account
  • 2004/2/19 19:43

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


I'd have to look more carefully, but I think you will need to use XoopsFormHidden; otherwise when the form is submitted, it would likely write a blank realname to the database.



22
mvandam
Re: Big security issue :: XOOPS
  • 2004/2/3 20:19

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


Yes, it sounds like your session was hijacked. Does your URL contain something like SID=1234sdg or SESSIONID=1234asdf or PHPSESSION=1234asdf etc??

Also, just another word of advice...

Use your administrator/webmaster account only for administrative type activities like changing permissions, installing/updating modules etc. Use a less privileged account for participating in forums etc.



23
mvandam
Re: Ratings System
  • 2004/2/2 21:44

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


risto:

About 6-8 months ago I implemented a ratings system for the core for integration into other modules, much like the comments/notification/etc systems. Unfortunately at the time it was rejected for inclusion in XOOPS (they wanted to combine ratings and comments).

I don't have the time to update this for the current Xoops, but if you're comfortable with PHP I can dig up what I was working on and send it your way if you want to try and get it working. Not the solution you're looking for I'm sure but let me know if you're interested.



24
mvandam
Re: Big BUG or problem in Xoops 2
  • 2004/2/2 0:39

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


This may be related to a problem where people can't send admin mail to a large group of users. Certain versions of PHP/Mysql/whatever cause a "memory exhausted" error when trying to manipulate a large group of users. If you can turn on the various debugging options, you can try to find out if you're getting the "memory exhausted" error (or simply increase the limit in php.ini from 8M to e.g. 16M and see if that works). There is no known solution for that problem (and the causes are also unclear) but if you're NOT getting that error then at least you can rule that out as a possibility.

See also:

https://xoops.org/modules/newbb/viewto ... hp?topic_id=14777&forum=7

https://xoops.org/modules/newbb/viewto ... p?topic_id=10304&forum=21

https://xoops.org/modules/newbb/viewto ... hp?topic_id=6528&forum=21

search forums for others...



25
mvandam
Re: Why are someone not using XOOPS?
  • 2004/1/27 2:45

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


Whoa Lots of interesting comments! I've also been playing around with some other CMSes; mostly just curiosity of what else is out there.

I'd have to say that so far, XOOPS is the easiest to understand. The code is very clear and it is relatively simple to figure out what does what and make any hacks you might desire. Also from a customization standpoint, it offers a lot of flexibility in controlling the 'look' of your site. While it is not as flexible as some others, it is definitely probably the easiest to customize which is very important.

Some other interesting CMSes to add to your list:

- xaraya - also a nuke derivative but seems to be heading towards a more integrated/unified way to do tasks which are common to many modules. I've had trouble installing it and getting it running though (haven't looked into it too much to figure out why). Also, IMHO, it appears somewhat slow.

- ez Publish - this is rather different than 'xoops'. You don't have 'blocks' etc to set up but rather you add certain types of content items to each page (or "container"). The system has a default way to show all the content items in a container, but each container can also be overridden with a template. This looks like a *very* powerful system, but it is also *very* complex and many things are not intuitive. In a sense, it seems to have *too much* flexibility and not limit things which won't make sense to most people.

- drupal - again this is rather different from 'xoops'. All 'content' is treated the same way. You assign content to 'categories' (called 'taxonomy terms'). There are special views for content based on what is most recent, what is in a particular 'taxonomy term', etc. You don't have individual block layout.

Anyways some of these are very different from XOOPS and will probably not suit certain types of websites or webmasters, but I mention them because I thought they had some interesting/advanced features.



26
mvandam
Re: New fields in member registration (register.php)??
  • 2004/1/26 23:12

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


Try searching the forums for "custom fields" or "user fields" etc... This has been asked many many times before . I think a couple people have some hacks...



27
mvandam
Re: Making Dynamic URLs Static
  • 2004/1/22 17:35

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


Quote:

This still misses the fact that what we are trying to do is eliminate the things that trip up most web crawlers, one of those being the presence of "periods" in the URL (the /index.php/ part in a directory list).

OK, didn't realize that. I thought it was just the arguments (i.e. characters '?' and '&' and '=') that were the problem.



28
mvandam
Re: Making Dynamic URLs Static
  • 2004/1/22 17:28

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


I have heard that a quite portable (i.e. works on many web servers) way to rewrite the URLs is something like:

http://example.com/index.php/articles/1/

(Note the presense of 'index.php'.)

I first saw this done in 'phpwiki'. Here is a little excerpt from the comments of the file index.php (in phpwiki):

Quote:

* PhpWiki will try to use short urls to pages, eg
* http://www.example.com/index.php/HomePage
* If you want to use urls like
* http://www.example.com/index.php?pagename=HomePage
* then define 'USE_PATH_INFO' as false by uncommenting the line below.
* NB: If you are using Apache >= 2.0.30, then you may need to to use
* the directive "AcceptPathInfo On" in your Apache configuration file
* (or in an appropriate <.htaccess> file) for the short urls to work:
* See http://httpd.apache.org/docs-2.0/mod/core.html#acceptpathinfo



29
mvandam
Re: Mantis Bug Tracker Problem
  • 2004/1/21 17:58

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


aivengo:
Good luck , and we definitely appreciate the offer to post the script here, thanks!



30
mvandam
Re: Mantis Bug Tracker Problem
  • 2004/1/20 19:46

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


aivengo:

The Mantis module currently only works the other way... XOOPS users accounts will be copied to mantis, but mantis accounts will not be copied to xoops.

However, they are not incompatible. If you give each user an XOOPS account (with same user name as in the mantis table), the accounts will automatically be synchronized.

If you have a lot of users, you could write a script to copy mantis user information into the XOOPS user table - as far as I know such a script does not already exist.




TopTop
« 1 2 (3) 4 5 6 ... 21 »



Login

Who's Online

71 user(s) are online (38 user(s) are browsing Support Forums)


Members: 0


Guests: 71


more...

Donat-O-Meter

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

Latest GitHub Commits