We have some cultures only by default,
I would like to add some custom cultures
Thanks
ex: en-IN is available
ar-IN I would like to add.
Related
I have checked the samples and read the documentation but did not get an idea on how we can customize or extend the default user management with our custom fields and some custom buttons in there to extend the default behavior.
Cofoundry does not currently support extensions to the user table, the feature is tracked by issue #176.
I have built an ecommerce website with Drupal 7 and use views and views filters for my product catalogue.
I would like to reduce the size of URL parameters for views filters to keep my URL's nice and short.
'Items_Per_Page' has no way of being changed in the UI.
I would like this to be changed to just 'Items'.
Can this be achieved?
Example
My product catalogue has 5 filters; Category, Mod, Brand, System, and Items Per Page.
The current URL is: catalogue/?category=All&mod=All&brand=All&system=All&items_per_page=All
I would like to change this to:
catalogue/?category=All&mod=All&brand=All&system=All&items=All
Please try the Better Exposed Filters module (https://www.drupal.org/project/better_exposed_filters). You can setup your custom filter identifiers in the view settings with this module in order to achieve want you want.
I was wondering how we can activate different themes on different pages dynamically.
For example few pages will have theme-1 and rest of the site will have theme-2. Users will not be selecting the themes. It will have to be set dynamically from the back end.
One way is to have separate master pages.
But is it possible that we have two nopCommerce themes and we activate any one dynamically on different pages of the same store? Not multi store.
It should be possible following these steps:
Create a new plugin.
Copy the current class ThemeContext, implementing IThemeContext to your plugin. Use a different name to avoid mistakes (see).
Register the new class with Autofac. Set a higher priority to ensure that the new class replaces the old ThemeContext. Enable the plugin and check it works by setting a breakpoint there.
Change the get part of the property WorkingThemeName in your new class and implement any business rules you need, returning the alternate theme name when appropriate. You may need to access the current RouteData to get the current route controller or parameters for each http request.
That's all. It is easier than it looks.
I'm currently setting my Drupal 7 site up in an additional language using the i18n and variable translation.
My problem is that I cannot update the title of the blog page or the URL alias when I switch to the version for the other language. When I switch language my posts are translated but I cannot find where to change the titles of the page or the URL alias.
I'd like the routes to look something like this:
mydomain.com/news
mydomain.com/es/noticias
There are different kind of translations supported in Drupal. By default translation is made buy matching nodes in different languages togheter. And adding new translation actually means making new node and matching it with rest marked together.
But also you can translate fields. So in this case you don't have different nodes, but field values are translated. And if I remember well you can't translate all fields, i.e. you can't translate title and path since it's one node. Is this a case?
Update:
You would need to add "title" module:
https://www.drupal.org/project/title
Check out please this article:
https://www.drupal.org/node/1280910
Hello I'm developping an application in Asp.net. One of my goals is to assign a theme to users (users can choose (between 2 themes) their own theme.
How can I achieve this?
thanks a lot
You can set a theme in the Page_PreInit handler like
Page.Theme = "MyGreatestThemeEver";
For keeping the selected theme you can either use Session, Profile, Cookies or a custom table in your database.