XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk


« 1 ... 17 18 19 (20) 21 »


191
mvandam
Re: Blank page after instalation

  • 2003/7/9 19:03

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


Quote:

Finally! an error message with that one! (I think this whole topic may solve lots of people's problems.)
Now what?


Hmmm, strange, it can't find one of your files. Does the indicated file exist on your server? Is it in the correct place? Looks like maybe the unzipping/uploading (however you get your files onto your server) didn't work properly... maybe try installing the files again and see if that fixes it.
Topic | Forum


192
mvandam
Re: Blank page after instalation

  • 2003/7/9 17:40

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


Do you have debugging turned on from XOOPS Administration preferences? (General Preferences | PHP Debugging)

If you're having trouble getting to admin page, you can edit include/common.php... around line 83, instead of 'error_reporting(0)', put 'error_reporting(E_ALL)'.
Topic | Forum


193
mvandam
Re: Blank page after instalation

  • 2003/7/9 16:53

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


Keep digging ... there is *always* an error message behind the blank page problem... There is really nothing we can do until you are able to produce an error message. *Many* different types of problems can result in an error, and all *fatal errors* lead to a blank page.

In particular, if you are running your own host, check php.ini and make sure "display_errors" is "on". If you are with a host provider, you can override this setting in a .htaccess file, if they run apache.
Topic | Forum


194
mvandam
Re: Configurable, optional, profile fields

  • 2003/7/6 22:10

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


Quote:

Everyone wants this feature, but no developer answers these questions or requests.


I know this is an old thread. This idea discussed sounds like a good one to me as well. To make sure devs read feature suggestions such as this (they don't have time to read *all* forum posts/threads), please post on sourceforge. First make sure nobody has already posted it, then outline in detail the feature... if you are familiar with XOOPS code, then any implementation ideas you have would be helpful as well.
Topic | Forum


195
mvandam
Re: INTO CVS: Brazilian Portuguese translation for Xoops 2.0.3

  • 2003/7/3 7:20

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


mikhail:

I just noticed there is already a brazilian portuguese language pack for XOOPS 2, but it has not been updated in the last 4 months. Were you involved in creating this? If so, it should be easy to make the upgrade. If not, we would have to contact the author of that other language pack and probably do a detailed comparison of the translations.
Topic | Forum


196
mvandam
Re: MassMail to members [not-quite fixed]

  • 2003/7/3 7:11

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


Quote:

yeah it runs apache, but I have no root access as it is a managed server, so in a way I have no restrictions on the usage, but can't edit the root.

I have no idea about .htaccess, apart from password and page not found things, but I'll look at the wikki you mentioned

Or do you mean creat a .htaccess with php_flag display_errors on in it, then place in that dir.


Tom,

Yeah, create a file .htaccess, and put that line as the only contents. I'm not sure this will work for your case but this is how I was able to finally see an error message on someone's site where the hoster had turned off all error display. The file needs to go in the directory where the script is *entered*... i.e. not the offending file. e.g. Mass mailing is accessed via XOOPS_URL/modules/system/admin.php?fct=mailusers, so the file should go in XOOPS_URL/modules/system/ even though the relevant file is probably elsewhere.

Hopefully there is some message that can help pinpoint the problem.

Looking at the error logs is also a good idea. Visit your website, try to mail users. This will make an entry in the log. It will list your IP so it might be handy to know this if this is a busy hoster and the logs accumulate quickly. Don't know about your hoster's setup, but on my system (Redhat linux), the log file is at /var/log/httpd/error_log. By default I think normal users have 'read' access.

Good luck
Topic | Forum


197
mvandam
Re: MassMail to members [not-quite fixed]

  • 2003/7/3 1:47

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


These warnings/notices don't look like they're important.

Does the 'sendmail' work, by the way, or is this what freezes now?

Quote:

now with the Debug on I get no errors but it freezes on a black page [...]


No messages? Hmmm, there must be a message hidden somewhere... Does your hoster run apache? If so, try putting "php_flag display_errors on" in a file ".htaccess" in either the root directory of your installation or modules/system/admin or modules/system/admin/mailusers/.
Topic | Forum


198
mvandam
Re: I would like to work on new translation for xoops 2.0.x

  • 2003/7/3 1:40

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


Thanks for your interest in contributing this! It is always nice to be able to make XOOPS available to additional users and a translation is a great help in this respect.

I'm sure even partial translations would be greatly appreciated by other korean-speaking users, if you are not up to the task of a full translation. I'm sure other volunteers would help to complete this project!

I would wait a day or two and see if anyone resonds to this thread... just to avoid duplicating any work in case someone else has started.

Quote:

One question though... will my language pack be available to other fellow Korean XOOPS users on this site once it is done?


Once a language pack is sufficiently complete (not necessarily all strings, but at least the most common/important ones), it can be added to the official XOOPS language distribution where it is available to everyone. I'll have to talk to Ono about it, but it might be possible to put it into CVS sooner (before it is done) so people could start to benefit from the partial translations earlier.
Topic | Forum


199
mvandam
Re: MassMail to members [not-quite fixed]

  • 2003/7/2 19:23

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


Hmm, 40M seems like quite a bit!! ... maybe you have a different problem... Have you tried to change your settings to get another error message instead of the 'server error' page? Among other things, this may involve creating an .htaccess file in your XOOPS directory to override the hosters php.ini settings... (instructions on wiki)

In another thread someone reported that 32M memory limit solved their problem for XOOPS 4.2.2 I believe, but I don't remember the number of users they had... maybe they are reading this and can post here...
Topic | Forum


200
mvandam
Re: MassMail to members [not-quite fixed]

  • 2003/7/2 18:10

  • mvandam

  • Quite a regular

  • Posts: 253

  • Since: 2003/2/7 2


Unfortunately I do not think this is due to any bug in XOOPS (nothing that I can find, at least), and I *suspect* this to be a memory issue with the earlier versions of PHP.

This is a wild guess, but I *suspect* that the later versions of PHP are more efficient at allocating a large number of objects.
Topic | Forum



TopTop
« 1 ... 17 18 19 (20) 21 »



[Advanced Search]

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

198 user(s) are online (118 user(s) are browsing Support Forums)

Members: 0

Guests: 198

more...

Donat-O-Meter

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

Latest GitHub Commits