I'm making a website for a bicycleshop.
The shop has different 'frames' and you can 'build' your own bike by choosing a frame and the components you want (groupset, wheel, pedals, ...).
In the back-end I have a content-type 'components' that exist of:
component-category
component-title
component-price
In the content-type 'bike-types' you can add multiple components to the bike-type (frame).
I was wondering whether it's possible to show the category of a component in the overview of the components in a bike-type entry.
Because now it's confusing that you've 'shimano 105' in the 'group' category and 'shimano 105' in the 'pedals' category.
Thanks a lot!
Karlien
You could update that components title to be dynamic and have a secondary field for it's actual title.
E.g. the title of the components could be {customTitle} - {category.title}
You can do this when editing the entry type.
Related
I am new to Umbraco CMS, so this question may sound silly. The requirement is to show the tags (based on a specific tag group) to editors in a dropbox, and they could able to choose these tags and save it to the article. What is the best way of achieving this?
The tag property allows free text entry. If you only want editors to select from a predefined list of options you will probably need to do this a different way. You may want to try the dropdown property with the multiple choice option turned on instead. Then you can setup the prevalues (options) ahead of time and your editors can only select from that list.
You could also create a container in the tree for your categories and then allow your admins to select the appropriate items from that list using a multinode tree picker. Here's kind of an example of how you might structure this for a blog:
Blog
Authors
Author
Categories
Category
Posts
Post
Then when an admin adds a new post you would allow them to select the appropriate authors/categories for the post using a multinode tree picker.
Does an equivalent of Wordpress “post types” and the Advanced Custom Fields plugin exist for Ghost?
As one example, I built a travel site that has multiple Trips (a custom post type), and each trip has various serialized itinerary destinations, tour guides, etc. Another example would be designer portfolios, where they might have a Projects post type, which contains serialized images, each with its own description and perhaps a date stamp or client or whatever.
Not supported and probably never will be. Seems like this doesn't have high priority in their team.
See: https://forum.ghost.org/t/custom-fields-for-posts/1124/46 and https://github.com/TryGhost/Ghost/issues/9020
We recently upgraded our Kentico 8.2 instance to 9.0 and are now focusing on localizing our site into two additional cultures. The textual content of our site is primarily stored in one of three places:
Editable regions
Text fields in custom page types
Custom tables
We're using the Kentico EMS license and would like to leverage the built-in Translation Services app in order to translate content in each of these locations, however it appears that it only supports with content within editable regions. I know Kentico has an input control for translating text boxes but it forces the content editor to create a distinct resource key for it; we simply have so much content I'm concerned this will get out of control for editors.
Additionally, we had considered migrating some of our content into pages but they don't logically fit there, and there are some complex relationships that would cause duplicate content so I'd really prefer to keep the content where it is. The other thought I had was to build either a custom module or custom form control to do some dirty work under the covers but didn't want to reinvent the wheel if there was already a known approach.
Is there a Kentico recommended approach, or workaround, to managing content translations within custom tables and page type fields?
You can use Translation in Kentico to translate page type fields and send them for translation. Check this documentation page for an example. It can be more complex at first, but it should do the trick for you. I have just tested creating a simple translation request for my page type and the resulting XLF file contained all page type fields.
For custom tables I will have to dissapoint you because custom tables in Kentico are not culture specific. If performance is important for you the best way to create translations is to add CultureCode field to your table in order to specify which culture the item is for.
For example you can have table with columns: ItemID, Text, CultureCode
And then the data would look like:
1, Dog, en-US
2, Hund, ge-GE
3, Pes, cs-CZ
If you would want to go even step further I would recommend to create this not as a custom table, but as a Custom class which will sit inside a custom module for which you can create your own interface which would allow editors to easily create all culture versions for the items.
For the custom page types and custom tables, you can change those text fields to localized text fields at the field definition and it will allow you to enter different values per language without a resource key. This is the best route IMHO for page types and custom table translation. Although this still does not allow for "automatic" or built-in translation.
I am not sure what do you mean by content translation in page type fields - there is support for translating page type fields. You can find example on sample site in Kentico installation. (The site is called DancingGoat - see image example for page type field localization in english and spanish language).
I need to set up a field in LocomotiveCMS that is similar to Select but allows multiple selections. Something like in HTML... does LocomotiveCMS allow for that, or will I have to do some ruby coding to get that to work?
Any help would be appreciated, thanks!
Old question but still a thing.
I'm unsure whether your question relates to fields within the Locomotive CMS Back Office or on the front end so I've addressed both below.
Front End
Irrespective of whether or not you're dealing with Locomotive CMS content types, either of the following will allow selection of multiple values on the front end:
Listbox (select element with the multiple attribute)
A series of checkbox inputs with the same value in the name property
Back Office
If you need to allow selection of multiple values within the Back Office, you can do this for content types using the has_many or many_to_many content type relationships.
If you need multiple value selection outside of content types (e.g. in metafields schema) you're unfortunately out of luck.
I'm new to Joomla so my comprehension of how it all works is a bit incomplete. I'd just like to know whether or not I need to add new menu items with an alias for all short urls used in the application (e.g. http://mysite/shorturl). What bothers me is that:
Why would I need to make a menu item for an alias if I don't use the item in a menu (why such a relationship between urls and menus).
If I had 50 articles using short urls (aliases), would I have to make a menu item for every single short url? There's some dependencies I don't like about that.
I thought it made sense to set the alias on an article level.
I read something about having to purchase an extension sh404-something for this - really?
If someone could help me out it would be much appriciated.
Thanks and regards,
Kjetil
Each article has its own unique url, even it's own unique SEF url. The only reason for have the menu item there is because there has to be a way to locally group and link things. Try this, create a category called "Things Starting with A" then create 3 articles and put them in that category. Create a menu item with a blog layout assigned to the category "Things Starting with A". When you click the menu item you should see your 3 articles, when you click their title you should see them on a single page with their own URL.