I am using phpged view since version 1.0 and have received with pleasure the announce of the new version 1.1.
This new version brings new stuff (and i like that) but i wonder if it had not be more interresting to make the more stable and robust before ?
As more and more people use this project, some restriction have (in my humble opinion) to be suppress :
- do not produce warning with a server having error_reporting = E_ALL
- improve the rendering with mozilla (the new 1.1 version messed up the pedigree chart)
- make it compatible with a server having safe-mode=on
Those improvements, which are not visible for the final user, may help the administrator in getting phpgedview working and help the developper team in its future work.
I put those remarks here as it is not a bug or a problem, but really an open discussion...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is still a great deal of work to do on PhpGedView. The items you note are just a few of them. Thank you for bringing them to my attention. I was not aware of the mozilla display problem which is worthy of bug status.
I'll see what I can do to get it to work in safe mode. I cannot make it work in all possible configurations of safe mode because safe mode allows the server administrators to turn functions on and off at will. You may also have to turn off a lot of the features because the functions they require have been turned off by the safe mode configuration.
I've been focusing my attention and support on two things. First, display issues. I feel it is most important to get the information in the gedcom displayed correctly. A very difficult task, but phpgedview gets better with every version released.
The second thing I have been working on is a mysql version for those people who would like improved performance on very large gedcoms. This has been a request since I first introduced phpgedview back in June 2002.
Another problem is that there is only one developer on the project, me :-) The project is starting to get to the point where one developer is not enough to support all requests in a timely manner. I hope to find some help soon.
Thanks,
--John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In fact, i have not realized that you are alone on this project. Well, congratulations for your work, so !
I totally understand your point of view, and know that you can't do a program which works everywhere !
My remark is more concern with the evolution of php itself. Each new release brings more restriction in the default php.ini configuration. And lots of ISP are using the default settings, just adding the safe mode. this is a trap for some projects...
But if you (the whole developper team !) are aware of it, i am confident that phpgedview will continue to do a good job for me !!
That is me who have to thank you !
--Julien
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've tried to address the issues you brought up in this post with the release of version 1.15.
I've fixed the problems with Mozilla and tried running it in safe-mode with error reporting set to E_ALL. I didn't really fiddle with the other setting of safe-mode, just tried to get it to work under the default configuration of safe-mode.
If this doesn't address all of the safe-mode problems let me know, because it is possible that I might have missed some of them.
--John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am using phpged view since version 1.0 and have received with pleasure the announce of the new version 1.1.
This new version brings new stuff (and i like that) but i wonder if it had not be more interresting to make the more stable and robust before ?
As more and more people use this project, some restriction have (in my humble opinion) to be suppress :
- do not produce warning with a server having error_reporting = E_ALL
- improve the rendering with mozilla (the new 1.1 version messed up the pedigree chart)
- make it compatible with a server having safe-mode=on
Those improvements, which are not visible for the final user, may help the administrator in getting phpgedview working and help the developper team in its future work.
I put those remarks here as it is not a bug or a problem, but really an open discussion...
There is still a great deal of work to do on PhpGedView. The items you note are just a few of them. Thank you for bringing them to my attention. I was not aware of the mozilla display problem which is worthy of bug status.
I'll see what I can do to get it to work in safe mode. I cannot make it work in all possible configurations of safe mode because safe mode allows the server administrators to turn functions on and off at will. You may also have to turn off a lot of the features because the functions they require have been turned off by the safe mode configuration.
I've been focusing my attention and support on two things. First, display issues. I feel it is most important to get the information in the gedcom displayed correctly. A very difficult task, but phpgedview gets better with every version released.
The second thing I have been working on is a mysql version for those people who would like improved performance on very large gedcoms. This has been a request since I first introduced phpgedview back in June 2002.
Another problem is that there is only one developer on the project, me :-) The project is starting to get to the point where one developer is not enough to support all requests in a timely manner. I hope to find some help soon.
Thanks,
--John
Thank you for you answer, john.
In fact, i have not realized that you are alone on this project. Well, congratulations for your work, so !
I totally understand your point of view, and know that you can't do a program which works everywhere !
My remark is more concern with the evolution of php itself. Each new release brings more restriction in the default php.ini configuration. And lots of ISP are using the default settings, just adding the safe mode. this is a trap for some projects...
But if you (the whole developper team !) are aware of it, i am confident that phpgedview will continue to do a good job for me !!
That is me who have to thank you !
--Julien
Hi Justin,
I've tried to address the issues you brought up in this post with the release of version 1.15.
I've fixed the problems with Mozilla and tried running it in safe-mode with error reporting set to E_ALL. I didn't really fiddle with the other setting of safe-mode, just tried to get it to work under the default configuration of safe-mode.
If this doesn't address all of the safe-mode problems let me know, because it is possible that I might have missed some of them.
--John