Because.... I didn't know about it! There is no mention of it in the Wiki and there was no place to put a URL when I created the SOUR. Yet it looks like PGV is expecting it. In fact it looks like it is expecting it either as 1 to the SOUR or 2 to the TITL. I like it as 2, personally.
I'll update the Wiki but unless I'm missing something people can only implement this by raw edit.
Thanks! I'll close the feature request.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anton
Who is using the source definition to navigate to that site?
and
Isn't that URL to general for a specific citation?
When used in the source reference for the INDI or FAM fact, it will work as expected when you use it as shown in Greg's source example directly above.
-Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've read through this entire thread and understand (somewhat) the developer's perspective.
However, I am "willing to take the risk" and would like to have (for my own, personal intents and purposes) the option;
to simplify the "Source Citation" process (which currently seems like a lot of redundant and confusing nonsense) to simply adding a "Note" to a field with a link to a remote (within the /home/PhpGedView/ directory structure) image, PDF or large text file.
e.g., Family Page View:
Marriage: date place
Note: Marriage Certificate
If indeed this is some sort of "Security Risk" I'm willing to take it given my personal usage.
There is only one and will only ever be one user w/ admin or edit rights - me.
Mine is Private and not viewable except by invitation.
I'm not suggesting or requesting a Blanket change in the software but I'm given to believe that this is not a terribly complex PHP edit so…
Would someone be willing to give me a little direction in making the necessary edit(s) to accomplish this?
- Public or Private, I don't care -
Further, just as a general question -
Is it not common place to allow/disallow specific HTML tags (arbitrarily)?
e.g., allow/enable: <a>, <b>, <i> etc…… disallow/disable: <script>
What about parsing (specified) BBCode for this purpose?
These questions arise from a long time use of Simple Machines forum software (prior to V2.0)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Darkstar
Only no replies to people with an attitude problem ;-))
It has been posted within several threads that there are no dedicated developers working on this project and support is limited to repairing security bugs and helping users with the software. It is hardly abandoned as a board, just a project that is a mature as it is going to be until someone comes along to take control. I, for one, am too busy to develop here as my time is with a much more dynamic replacement that forked from this project.
BTW, PGV handles most URL's just fine, but only in certain places and manners in which, from experience we know that a hacker will try to take over your site. We don't publicize these, but I can assure you there have been many breeches.
None we currently know about…Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Because.... I didn't know about it! There is no mention of it in the Wiki and there was no place to put a URL when I created the SOUR. Yet it looks like PGV is expecting it. In fact it looks like it is expecting it either as 1 to the SOUR or 2 to the TITL. I like it as 2, personally.
I'll update the Wiki but unless I'm missing something people can only implement this by raw edit.
Thanks! I'll close the feature request.
Anton
Who is using the source definition to navigate to that site?
and
Isn't that URL to general for a specific citation?
When used in the source reference for the INDI or FAM fact, it will work as expected when you use it as shown in Greg's source example directly above.
-Stephen
I've read through this entire thread and understand (somewhat) the developer's perspective.
However, I am "willing to take the risk" and would like to have (for my own, personal intents and purposes) the option;
to simplify the "Source Citation" process (which currently seems like a lot of redundant and confusing nonsense) to simply adding a "Note" to a field with a link to a remote (within the /home/PhpGedView/ directory structure) image, PDF or large text file.
e.g., Family Page View:
Marriage: date place
Note: Marriage Certificate
"Marriage Certificate" being the (hyperlink) result of
<a href="http://my_domain.com/phpgedview/repository/specific_image_sometimes-quite-long.jpg" target="_blank">Marriage Certificate</a>
i.e., any "Note" field to parse the anchor tag.
If indeed this is some sort of "Security Risk" I'm willing to take it given my personal usage.
There is only one and will only ever be one user w/ admin or edit rights - me.
Mine is Private and not viewable except by invitation.
I'm not suggesting or requesting a Blanket change in the software but I'm given to believe that this is not a terribly complex PHP edit so…
Would someone be willing to give me a little direction in making the necessary edit(s) to accomplish this?
- Public or Private, I don't care -
Further, just as a general question -
Is it not common place to allow/disallow specific HTML tags (arbitrarily)?
e.g., allow/enable: <a>, <b>, <i> etc…… disallow/disable: <script>
What about parsing (specified) BBCode for this purpose?
These questions arise from a long time use of Simple Machines forum software (prior to V2.0)
Love the support!
Thanks for nothing. I figured it out.
Since the board has quite obviously been abandoned posting should be turned off.
Darkstar
Only no replies to people with an attitude problem ;-))
It has been posted within several threads that there are no dedicated developers working on this project and support is limited to repairing security bugs and helping users with the software. It is hardly abandoned as a board, just a project that is a mature as it is going to be until someone comes along to take control. I, for one, am too busy to develop here as my time is with a much more dynamic replacement that forked from this project.
BTW, PGV handles most URL's just fine, but only in certain places and manners in which, from experience we know that a hacker will try to take over your site. We don't publicize these, but I can assure you there have been many breeches.
None we currently know about…Stephen