In my module's xml file, I have a fieldset for ADVANCED OPTIONS like this:
<fieldset name="advanced">
<field .... />
<field .... />
<field .... />
</fieldset>
In Joomla 2.5, the ADVANCED OPTIONS of my module correctly shows all the fields as described in the xml.
However in Joomla 3.x, the ADVANCED OPTIONS shows all the fields from the xml file plus some extra options. Even if I totally remove this fieldset, it still shows the ADVANCED OPTIONS with some default fields.
How do I make sure both Joomla 2.5 and 3.x have the same ADVANCED OPTIONS?
Related
I need to remove the create button in kanban view which found in "Sales/Customers" as in below image
In your kanban declaration add create="false" just like you see below.
<kanban create="false">
You can just go into settings->user interface->views and edit this directly. You also may be able to activate developer mode by clicking on your username (in the top right of the screen v8 or he little question mark v9+) and select About Odoo then activate developer mode. From there you should also be able to edit the form view (if you have admin authority).
You can also create an addon which modifies this view using xpath. Similar to this.
<record model="ir.ui.view" id="modified_partner_form_view">
<field name="name">partner.modified</field>
<field name="model">res.partner</field>
<field name="inherit_id" ref="base.view_partner_form"/>
<field name="arch" type="xml">
<xpath expr="//kanban" position="attributes">
<attribute name="create">false</attribute>
</xpath>
</field>
</record>
Note: setting create to false should work however using the webconsole did not allow me to add the attribute to the kanban tag. I am not sure why, it should work but in my installation would not. The xpath method should work, I have used it to modify other attributes however have not tested with this kanban create attribute. If someone knows why this might not work please comment. Thanks
i want to translate the submit value of the login joomla module
<input type="submit" name="Submit" class="button" value="<?php echo JText::_('JLOGIN') ?>" />
Exactly where can i find "JLOGIN" text and thnks in advance.
In Joomla 1.6 or above there is a user interface for overriding specific language strings in the language manager. Go to the language manager and select the overrides tab. There are detailed instructions for use in the UI.
These are always defined in your language ini files. A quick search shows: language/en-GB/en-GB.ini. The en-GB directory will vary depending on your default language.
The current value of this text is Log in, for en-GB that is.
I've been reading a lot of posts about unobtrusive validation. I'm trying to understand the difference (if any) between what visual studio provides in an empty MVC3 template and including the jquery.unobtrusive js files. At present this is what my inputs in the source look like
<input class="input-validation-error" data-val="true" data-val-required="The Surname field is required." id="Surname" name="Surname" type="text" value="" />
Is this unobstrusive validation?
With the data- attributes in your HTML syntax, it looks like your page is enabled for unobtrusive client-side validation.
With the traditional client-side validation javascript for the controls to be validated are generated at the server-side and passed on along with the HTML in the Response to the browser.
Hence in addition to the HTML content there will be inline script data embedded within <![CDATA[ ]]>
However with unobtrusive client-side validation instead of emitting inline javascript, it makes use of HTML5 compatible Data attributes
ASP.NET MVC 3 make use of jQuery for unobtrusive client-side validations. data- attributes will be manipulated from jQuery functions defined within jquery.unobtrusive js
By default unobtrusive mode is turned off in ASP.NET MVC 3. To make use of this you will need to enable both client-side validation & unobtrusive javascript validation.
This can be set in web.config
<configuration>
<appSettings>
<add key="ClientValidationEnabled" value="true"/>
<add key="UnobtrusiveJavaScriptEnabled" value="true"/>
</appSettings>
</configuration>
Short answer yes it looks like you use unobtrusive validation. To have a deeper understandig of what it is and how it works please have a read http://bradwilson.typepad.com/blog/2010/10/mvc3-unobtrusive-validation.html
MVC outputs the data-* attributes and jquery provides the actual client side implementation if looking for those attributes.
http://completedevelopment.blogspot.com/2011/02/unobstrusive-javascript-in-mvc-3-helps.html
I would like to configure my frontpage (default page). In Menu Manager I set Menu Item Type to "Featured articles". It's great. I have featured articles on my homepage. Now I want to show my special module only on my homepage. So I add new module in module manager and assign it to homepage. Yes, module is added. And this is problem. Module is added before Featured Articles.
I would like to change order of Featured Articles (Content Component) and Modules. Is it possible?
I think I can't change it in Joomla Back-end.
Thank you very much for reply
Oh, it's my mistake.
In my main template file index.php I have bad order of jos:include tags.
<jdoc:include type="component" />
<jdoc:include type="modules" name="left" style="mfPanel" headerLevel="2" />
First it must be component and then tag for modules.
Is there a way to specify a layout update for a specific category (e.g. using category ID) without having to use the administration dashboard, and setting a [Custom Design > Custom Layout Update].
I am sure I can create a module that looks for a category ID and switches the layout based upon that, but I was curious if there was a naming or some other type of convention for layout files that allows for this type of granular control since Zend Framwork sometimes allows such naming conventions.
Also maybe within the catalog.xml file itself there are additional "layouts" that allow such granularity, something more specific than <catalog_category_layered />
In a standard Magento install (1.4.2, but it should apply to the rest), Magento issues the following Layout handles (handles tell Magento which Layout Update XML Fragments to load from the Package Layout)
<default />
<catalog_category_layered_nochildren />
<STORE_default />
<THEME_frontend_default_default />
<catalog_category_view />
<catalog_category_layered />
<CATEGORY_4 />
<customer_logged_out />
The following layout handle
<CATEGORY_4 />
is generated based on the ID for a category. This means you should be able to add something like the following to your local.xml, or to a custom layout XML file added via a custom module
<layouts>
<CATEGORY_4>
<!-- your UPDATE xml here -->
</CATEGORY_4>
</layouts>
When visiting a catalog category, Magento loads a handle for CATEGORY_${ID}, which you can use to do exactly what you are asking.