CVS edit link for jacksinn
I have developed a module (JPIIM) that accepts a URL, performs a CURL request, caches the contents, and then displays the cached contents in its respective block. It was created to manage all different URL-based blocks on a site in one location and creates an easily identifiable block name. This is especially useful when managing a large site.
Future development plans for the JPIIM module are to have a dynamically generated form form element when configuring the items so that a site is not limited to only using the current 5 slots (without otherwise changing the code, of course).
I am open to using GPL v3 as well. I do not release source that is not GPL compliant.
Comments
Comment #1
jacksinn commentedThe JPIIM module was written by Steven C Jackson and Roger Soper.
Comment #2
avpadernoRemember to change the status, when you upload new code.
Comment #3
avpadernoThe comment before a hook implementation usually reports which hook is implemented by the function.
Menu titles, and descriptions should not be passed to
t()because that is already done by Drupal core code.Titles should use a capital case word as first word, while the other words should be lower case words (with the exception of proper nouns, and acronyms).
The description is not useful, if it repeats what said in the title of the form field.
There is a Drupal function that can be used to scan the files contained in a directory.
To do what the module does, there is no need to use the module. It would be enough to create a custom block; doing so, I would not be limited to use 4 blocks, but I would be able to create any blocks I would.
Comment #4
jacksinn commentedThanks for the feedback - I'll update the current issues. I've implemented some code to generated the necessary directories when the module settings page is called. Some users had a problem of it not creating a directory.
I agree that at the face, the use of this module seems as if it something I could do in blocks without the current 5 block limitation. That was my actually my argument against creating this module in the first place. What this modules intent is, however, is to provide an easy interface for non-programmers dealing with large content websites and want an easy place to just paste in a URL and a description which in turn generates blocks with the content locally cached.
My next iteration is to use AHAH or a similar mechanism to create limitless URL inputs.
Comment #5
jacksinn commentedUpdated hook comments.
Removed t function where not necessary.
Updated output to only have caps on first word and proper nouns.
Made descriptions more descriptive.
Changed cache clearing mechanism to use file_scan_directory().
Creates cache directories if they don't exist upon loading settings page.
Comment #6
jacksinn commentedAdded dynamic/unlimited JPIIM element functionality.
Added textfield to set title.
Added 'remove option'.
This module was created to remove the need for PHP knowledge and block management for non-programmers to be able to include external site elements in their own sections. The module fetches the code and locally caches it and makes external requests manageable in one location.
Comment #7
jacksinn commentedComment #8
jacksinn commentedComment #9
avpadernoComment #10
avpadernoSee the Drupal coding standards to understand how a module code should be written. In particular see the suggested formatting.
Some strings are not translated.
Comment #11
avpadernoThere have not been replies from the OP in the past 7 days. I am marking this report as .