Resource icon

[Tutorial] Modding the Resource Manager to an Article Manager

hmmm how i can remove the description and the version

i remove the code but when i go to try it its says that i need to put the version number and need to write description

is there way to skip them

the code i remove

HTML:
<dl class="ctrlUnit">
            <dt><label for="ctrl_tag_line">{xen:phrase tag_line}:</label></dt>
            <dd>
                <input type="text" name="tag_line" value="{$resource.tag_line}" class="textCtrl" id="ctrl_tag_line" maxlength="100" />
                <p class="explain">{xen:phrase provide_very_brief_one_line_description_of_your_resource}</p>
            </dd>
        </dl>
remove version number

HTML:
<input type="text" name="version_string" value="{$resource.version_string}" class="textCtrl" id="ctrl_version_string" maxlength="25" placeholder="{xen:phrase version_string}" />
<p class="explain">{xen:phrase name_by_which_resource_known_and_version}</p>


remove type

HTML:
<fieldset>
<dl class="ctrlUnit">
<dt><label for="ctrl_version_string">{xen:phrase resource_type}:</label></dt>
<dd><ul>
<xen:if is="{$category.allow_local}">
<li><label><input type="radio" name="resource_file_type" value="file" id="ctrl_resource_file_type_file" class="Disabler" {xen:checked '{$resourceType} == "local"'} /> {xen:phrase uploaded_file}:</label>
<ul id="ctrl_resource_file_type_file_Disabler">
<li>
<xen:include template="file_uploader">
<xen:set var="$buttonText">{xen:phrase upload_your_resource}</xen:set>
<xen:set var="$attachmentButtonKey">resource</xen:set>
</xen:include>
</li>
</ul>
</li>
</xen:if>
<xen:if is="{$category.allow_external}">
<li><label><input type="radio" name="resource_file_type" value="url" id="ctrl_resource_file_type_url" class="Disabler" {xen:checked '{$resourceType} == "url"'} /> {xen:phrase external_download_url}:</label>
<ul id="ctrl_resource_file_type_url_Disabler">
<li><input type="url" name="download_url" class="textCtrl" /></li>
</ul>
</li>
</xen:if>
<xen:if is="{$category.allow_commercial_external}">
<li><label><input type="radio" name="resource_file_type" value="commercial_external" id="ctrl_resource_file_type_commercial_external" class="Disabler" {xen:checked '{$resourceType} == "commercial_external"'} /> {xen:phrase external_purchase_and_download}:</label>
<ul id="ctrl_resource_file_type_commercial_external_Disabler">
<li>
<input type="url" name="external_purchase_url" id="ctrl_external_purchase_url" class="textCtrl" placeholder="{xen:phrase purchase_url}"
/><input type="text" name="price" id="ctrl_price" class="textCtrl" placeholder="{xen:phrase price}"
/><select name="currency" class="textCtrl" id="ctrl_currency">
<option value="usd">USD</option>
<option value="cad">CAD</option>
<option value="aud">AUD</option>
<option value="gbp">GBP</option>
<option value="eur">EUR</option>
</select>
</li>
</ul>
</li>
</xen:if>
<xen:if is="{$category.allow_fileless}">
<li><label><input type="radio" name="resource_file_type" value="fileless" {xen:checked '{$resourceType} == "fileless"'} /> {xen:phrase does_not_have_file}</label>
<p class="explain">{xen:phrase body_of_this_resource_should_be_provided_in_description}</p>
</li>
</xen:if>
</ul></dd>
</dl>
</fieldset>

=( but i dono how to skip them
 
How involved will upgrades be after making these modifications?

To be honest, seeing all these edits ensures me that upgrading the Resource Manager will be a giant pain in the ass ;)
Many template edits and phrase edits.. However, with the Template Modification System this might be easier.
 
That's what I figured. I wonder if there's a smarter way to implement this. I REALLY like the idea.
 
I am also wondering this as I made a good edit on the RM but never yet used TMS.
I'm also looking at Xenzine. This is a lovely addon with a good dev. The only negative is it being an addon. A TMS adjusted RM might be more reliable longer term.
Though I really dont know why XF couldn't do it as an option. People have been yelling for an article system for years. The RM is very close.
 
Just FYI, I'm not going to update this for the next RM version because it's a dirty implementation. Perhaps the 1.1.X series of the RM will have article features, though.
 
Back
Top Bottom