Support/Comments for Doc Finder Module

I just installed DocFinder using the instruction and now when I click on the Doc Finder button under the modules tab and get a blank page. Nothing renders, I tried re uploading all of the files and it doesn’t help.

include($modx->config['base_path']."assets/modules/docfinder/index.php"); 

You might check to see if the php short_open_tag option is turned off in the php.ini file. (You can create a file with nothing but this in the content to test it: <?php phpinfo(); ?>) If short tags are off, the module won’t work until you either turn short tags on (not recommended) or search and replace all the short tags with long tags (see the last paragraph of my previous post above).

I guess you forgot to paste the module code when you created the Doc Finder Module?

include($modx->config['base_path']."assets/modules/docfinder/index.php"); 

Is there anyway i can check to see if the file is being pulled in?

<?php die('yes, it was included.'); ?>

include '/home/user/public_html/assets/modules/docfinder/index.php';

Quote from: betoranaldi at Dec 05, 2008, 12:35 PM

Is there anyway i can check to see if the file is being pulled in?

Put this line at the very top of the Doc Finder index.php file:

<?php die('yes, it was included.'); ?>

That will tell you if it was included or not (you’ll need to remove the line later).

If it is not included, try typing the full path in the call to the module. It might look something like this:

include '/home/user/public_html/assets/modules/docfinder/index.php';

Of course, you have to get the path right, or it won’t work.

betoranaldi, can you check if the Doc Finder index.php file is all in one line? This can happen on some systems / with some software because of the different types of line endings. As the index.php file starts with a comment (//) everything in there would be considered to be a comment if there is only one big line.

I took a look at your updated code. I see that you added the call to the OnBeforeDocFormSave and OnDocFormSave events. The way the code is set up now, though, you’re assuming that the only events that need to be invoked are those two. But if the user is replacing content in a snippet or chunk or TV or something else, your script will not work as intended. You will need to use the other events too:
OnBeforeChunkFormSave,
OnChunkFormSave,
OnBeforeSnipFormSave,
OnSnipFormSave,
[...]

Yes you are right, I have to distinguish between the different types of content that re replaced and this would be easy to handle. But another thought just came into my mind: all the events have to do something with "form" (OnBeforeDocFormSave, OnChunkFormSave, ...). After thinking about it I am not sure if I should trigger this events in the Doc Finder code at all as I am not handling with the form in any way but write the replaced content directly to the database.

The question is if this events are indeed closely related to the manager (form) or are also meant to be triggered when the database is directly manipulated. Maybe someone of the core developer team can help us with this question.

$modx->invokeEvent("OnBeforeDocFormSave", array (
    "mode" => "upd",
    "id" => $id
));

$modx->invokeEvent("OnBeforeModFormSave",
    array(
    "mode"	=> "upd",
    "id"	=> $id
));