1
jDiction Forum
- October 14, 2024, 08:02:00 am
- Welcome, Guest
News:
jDiction 2.2.0 released. http://jdiction.org/downloads
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
8
Extension plugins / Advanced Module Manager (com_advancedmodules)
« on: August 01, 2014, 04:31:38 pm »10
Extension plugins / XML Specification
« on: August 01, 2014, 04:16:48 pm »
This is the documentation for the xml File used by jDiction to support 3rd party extensions.
Thx to pagchen and pipedream for creating most part of this post.
A jdiction.xml file should be created inside administrator/components/com_<COMPONENT>/.
<tables> tag
Locate the model file, such as administrator/components/com_<COMPONENT>/tables/<TABLE>.php.
The <table><file> tag should contain the name of this file and in its content we can also find the values for the tags:
The tag <table><exportfilter> is optional and allows you to filter records through an SQL query when exporting the table.
<views> tag
In you administrator's panel visit the component and get the view/task and layout values of the URL of the listing and editing pages.
The <view> tag should have the following attributes:
Regarding the fieldset, fields and field tags, these should follow what is described in Joomla! Documentation:
http://docs.joomla.org/XML_JForm_form_definitions
NOTE: there are some things missing in Joomla documentation, such as:
- in order to avoid that HTML from an Editor form field type is filtered, it is necessary to add the attribute filter="JComponentHelper::filterText"
Still, there are some aspects worth mentioning:
Thx to pagchen and pipedream for creating most part of this post.
A jdiction.xml file should be created inside administrator/components/com_<COMPONENT>/.
Code: [Select]
<?xml version="1.0" encoding="utf-8"?>
<jdiction>
<component>com_<COMPONENT></component>
<sections>
<section>
<tables>
<table>
<name>#__db_table</name>
<key>db_table_key</key>
<class><COMPONENT>Table</class>
<file><COMPONENT>.php</file>
<cache fullfetch="0" />
<exportfilter/>
</table>
</tables>
<views>
<view name="edit_view" list="list_view" layout="edit_layout" default="true">
<form import="<FORM>.xml">
<fieldset name="main" label="COM_JDICTION_TRANSLATION_FIELDSET_MAIN">
<field name="<A_FIELD>" />
<field name="<ANOTHER_FIELD>" />
</fieldset>
<fields name="extra_fields">
<fieldset name="extra" label="ANOTHER_TRANSLATION_STRING">
<field name="an_extra_field" />
</fieldset>
</fields>
</form>
</view>
</views>
</section>
</sections>
</jdiction><tables> tag
Locate the model file, such as administrator/components/com_<COMPONENT>/tables/<TABLE>.php.
The <table><file> tag should contain the name of this file and in its content we can also find the values for the tags:
- <table><class>, within the code "class <COMPONENT>Table extends JTable";
- <table><name>, within the code "parent::__construct('#__db_table', 'db_table_key', $db);";
- <table><key>, within the code "parent::__construct('#__db_table', 'db_table_key', $db);".
The tag <table><exportfilter> is optional and allows you to filter records through an SQL query when exporting the table.
<views> tag
In you administrator's panel visit the component and get the view/task and layout values of the URL of the listing and editing pages.
The <view> tag should have the following attributes:
- name, value of the view/task parameter in the editing URL:
"/administrator/index.php?option=<COMPONENT>&view=edit_view" or
"/administrator/index.php?option=<COMPONENT>&task=edit_view.edit_layout"; - list, value of the view/task parameter in the listing URL:
"/administrator/index.php?option=<COMPONENT>&view=list_view" or
"/administrator/index.php?option=<COMPONENT>&task=list_view.list_layout"; - layout, value of the layout parameter in the editing URL:
"/administrator/index.php?option=<COMPONENT>&task=edit_view.edit_layout" or
"/administrator/index.php?option=<COMPONENT>&task=edit_view&layout=edit_layout"
(if the layout parameter is not defined, the value "default" should be used); - default, when equal to true it should allow translations on the default component page (without any view/task parameter defined, such as "administrator/index.php?option=<COMPONENT>), seems to be useful only when the default task is not the editing or listing because for these it would be enough to specify as "default" its attribute (name or list, respectively).
Regarding the fieldset, fields and field tags, these should follow what is described in Joomla! Documentation:
http://docs.joomla.org/XML_JForm_form_definitions
NOTE: there are some things missing in Joomla documentation, such as:
- in order to avoid that HTML from an Editor form field type is filtered, it is necessary to add the attribute filter="JComponentHelper::filterText"
Still, there are some aspects worth mentioning:
- fieldset tag must have a name attribute and, if a XML form definition file is imported, its value or the value of an additional attribute named reffield should be the same as the one set in the file;
- field tag can have an alias auto-generated from another field by setting the following attributes and values: type="jdalias" and field="source_field_name" (usually source_field_name is "title");
- export of a particular field can be disabled if its attribute export is equal to "false";
- field tag can accept a pair of attributes for holding multiple table columns: the multifield attribute holds the column names (separated by commas) and the seperator attribute defines what separates each column value inside the field; for now, this feature seems to only work with the Joomla content table;
- fields tag can be used for handling multiple fields stored as a JSON format string in a single table column.
11
General Questions / Database Type
« on: October 16, 2013, 11:16:33 am »
A PM with an important question
You can't install another component that needs a different database driver. The problem is that jdiction, like other multilang components, intercepts the database queries and modifies the query and or the result.
I don't know any other component that need its own database driver, because there is no need to ;-)
But if there is really an awesome component that is a must for many people, I will try to support this component too.
hi sir!
i've installed your component and have a feeling that it will do the best for me and i'll try to do something good for you back
but here is the thing, in order to make component to work, i needed to change Database Settings from Mysqli to Jdiction_mysqli.
is that ok? what if tomorrow i'll have to install another component, which will want it's own database type too, what is then?
thank you in advance,
best regards
You can't install another component that needs a different database driver. The problem is that jdiction, like other multilang components, intercepts the database queries and modifies the query and or the result.
I don't know any other component that need its own database driver, because there is no need to ;-)
But if there is really an awesome component that is a must for many people, I will try to support this component too.
12
General Questions / Prerelease for 0.9
« on: February 01, 2013, 07:37:02 pm »
Version 0.8.3 could be found at http://jdiction.org/en/downloads
Changelog: http://jdiction.org/en/component/content/article/16-downloads/jdiction-package/30-jdiction-0-9
Changelog: http://jdiction.org/en/component/content/article/16-downloads/jdiction-package/30-jdiction-0-9
13
General Questions / Welcome to jDiction Forum
« on: May 13, 2012, 07:17:14 pm »
Please post your questions and help other people to solve there problems if you can.
Pages: [1]