752
You are correct - the htaccess file cannot be used to set the max file upload size. It needs to be done in php.ini by the host (or you, if you have access)
754
Actually, the project is now hosted on XOOPS Dev site - pgvxoops dev.
There are instructions in the readme-xoops.txt included with the module. The code on the dev site is really a wrapper for the pGV code.
Try it out and see if this is what you are looking for.
[Edit] I listed the wrong readme, I have corrected in the post [/edit]
There are instructions in the readme-xoops.txt included with the module. The code on the dev site is really a wrapper for the pGV code.
Try it out and see if this is what you are looking for.
[Edit] I listed the wrong readme, I have corrected in the post [/edit]
755
There was an initial release of the pgvxoops that included an incorrect setting in the sql/mysql.sql file causing a problem in one of my environments.
If you can use phpMyAdmin to look at your database, check the <xoopsprefix>_pgv_individuals table, and look at the i_isdead field. If the attribute UNSIGNED is set, you will have problems with the permissions functions. Change the attribute, update the field to be '-1', then go back to your pgv pages and check the display. You can also change the length of the field to 1 instead of 11.
Let me know if this helps.
If you can use phpMyAdmin to look at your database, check the <xoopsprefix>_pgv_individuals table, and look at the i_isdead field. If the attribute UNSIGNED is set, you will have problems with the permissions functions. Change the attribute, update the field to be '-1', then go back to your pgv pages and check the display. You can also change the length of the field to 1 instead of 11.
Let me know if this helps.
756
You can do it without a redirect - edit the paths in your index.php, but also edit the XOOPS_URL and XOOPS_ROOT_PATH in mainfile.php (mine is is /xoops folder)
759
As the administrator, you can change them, but not know what the existing passwords are. If you look in the users table, you will only see the encrypted passwords.
760
Here's a few good things that came out of this thread (good, IMHO)
* Skalpa committed to increasing the default for minimum length of username and password
* Monty provided code to keep users from changing their display name, leaving it under the control of the administrators
* Talk of including maximum attempts before being locked out (via Protector or core code)
Overall, the discussion should lead to XOOPS improvements. Exactly what we need.
* Skalpa committed to increasing the default for minimum length of username and password
* Monty provided code to keep users from changing their display name, leaving it under the control of the administrators
* Talk of including maximum attempts before being locked out (via Protector or core code)
Overall, the discussion should lead to XOOPS improvements. Exactly what we need.
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 |
 |
|