I am in the midst of setting up an internal wiki (Screwturn V3.0.5.600) for my department. I'm at the point of setting up the basic structure and I believe I will need both categories and sub-categories.
I've gone through the documentation and I have not found instructions on setting up sub-categories. Is it possible? Is there perhaps a plugin that makes it possible?
I gave setting up my major categories as namespaces and then my subcategories as categories in each namespace, but that just didn't feel right.
Thank you, in advance, for your assistance.
I don't believe there's currently any real way to harness subcategory functionality in STW. If you explained more what your structure is and why you need it set up that way, perhaps people could offer suggestions.
Offhand, you could try to set up semantic sub-categories by giving different categories related names. I.e., 'Development', 'Development-project1', 'Development-project2'.
Aside from that, what about using the keywords functionality?
Related
I work in a hospital and I participate in the creation of our new website.
We have nearly 40 departments, and each has 1 to 10 specialties. For each specialty, we would like to have 3 to 10 pages to describe in detail what the hospital offers our patients.
My question is: what do you think is the best way to create these pages?
Do I have to create simple pages and just take care about the
hierachy between them?
Do I have to go through new content types?
Do I have to go through a module that I have not yet found that allows me to obtain this?
Thank you in advance for the leads you can give me!
Long live the Stackoverflow community! : D
The proper way would be to create custom post type and taxonomies for your goal. You can go with pages too but that have its own restrictions such as having archive,defining own single pages, taxonomy pages etc. If you want to have custom fields its also good practice to keep them for your specific post type otherwise could get messy realy quick. Also create your functions with ability to be edited in future. This will take a bit of time to code it but in future will save you much more time. And add comments!!! in your theme.
To make your Work Easy and Fast use Pre Made Divi Child Theme. You can just Edit it using Drag & Drop Option. Below are Some Example which May Help you
Medical Fusion
Divi Smile
If you don't know how to edit feel free to ask us Tech Gigs
I've yet to find that 2sxc has facilities for entering, browsing, filtering and otherwise allowing keyword based filtering/sorting. If so, is there documentation about this, or sample code perhaps?
I'd think it might also be likely that one could use DNN's pretty good capabilities for tags and categories, and also razor queries would enable this, but I'd sure love to see some examples/guidance on best practices for doing so from within 2sxc.
This is very easy to do, but it's much more advanced that just tags / categories.
Basically you
Create a new ContentType for the related information - like Tag, Category or whatever. It can have more fields than just a title, as a category could also have an icon
Add some of that data
Go to the content type where you want to use it, create a "Entity / Content-Item" field
Then go to the field settings, give it the name of the related info that is allawed and if 1 or more items may be added (category is often just 1, Tags is often many)
that's it :)
I think I've found a start on this at:
http://2sxc.org/en/Docs-Manuals/Feature/feature/2685
and the demo at
http://2sxc.org/dnn-app-demos/en/Apps/FAQ-with-Categories
I've recently taken on a project from a client of mine, after a lot of persuasion I've managed to finally get the website under some kind of CMS. I'm pretty new to Wordpress I've come from an ExpressionEngine background and fancied trying something new for a change, so excuse the lack of knowledge (I'm trying my best! :D).
Now The issue I'm currently facing is that they have very specific directions regarding how they want their content displayed on their website and more importantly how they would like to manage it. They are a travel agent I'm currently putting together the resort directory that will display all of the resorts they offer.
In regards to the current structure of the directory it will be made up of 4 different sections. To give you a better understanding of how I want things to work take a look at this hierarchy below, (I've used turkey as an example, these would need to be dynamic):
/destinations/ This will be our destinations page that will list
all of the countries they currently
offer. I imagine this to be a static
page with some content about the
countries on offer with a list of the
countries below (These will be our
parent taxonomies).
/destinations/turkey/ This will be our parent taxonomy. This
page will also have to have the
ability to add some static content to
insert information about the country
and its locations. Below this will be
a second list, these will be the
different areas of turkey (These will
be children of the parent
taxonomies).
/destinations/turkey/belek/ This will be our child taxonomy, This
page will again need to have the
ability to add some static content.
It will also include our list of
resorts that my client offers within
this location (These will be our
entries/posts).
/destinations/turkey/belek/resort-name
This will be our post/entry page,
here we will have all of the
information on the select resort, the
specifics of this aren't an issue and
I've already got this sorted.
Now, I've done a lot of reading up on custom post types, custom taxonomies and their abilities and uses but I'm hit with a situation at the moment where I can't decide on which route I should take. I've been experimenting over the last few hours with the setup of one custom post type (for resorts) and one hierarchical taxonomy (for locations). Which works some what ok BUT due to the limitations of the taxonomy UI within the admin panel it doesn't allow me to add my static content/images etc. (I'd much prefer to use a WYSIWYG especially from a clients point of view).
So this makes me wonder if it would be worth making two custom post types and scrapping taxonomies all together, making one of the post types resorts and the other locations. With the locations post type I could set it up like the pages module (which would give me hierarchical controls to allow me to organise my locations how I had originally planned) but is this a wise move? I mean from what I've read you shouldn't really organise content this way but I've got a feeling that maybe just a clash of contextual semantics (I could be wrong!). Would there be any limitations for me setting things up this way should I wish to add search functionality in the future? Or anything else for that matter?
I thought I'd mention this before I FINALLY click the submit button (apologies for the great wall of text) but pages... I've read here that they are powerful little gems within Wordpress, how should I be taking advantage of these if I'm using custom taxonomies? How well do they work with listing categories are they what I need?
Right, that about wraps up everything I've got to ask for now - maybe I should have split this into a few posts but hey! I hope this gives you guys enough information about what I'm trying to achieve and please if I am going wrong feel free to point me in the right direction I'm really eager to learn more about Wordpress and it's capabilities.
Regards
Danny
While this is one approach, it sounds like what you really want to be using (rather than custom post-taxonomies) is simply the Page functionality of WP. Everything you're describing is simply the hierarchical structure of the navigation of your pages. Yes, you can use the custom taxonomies to accomplish this same thing, but since you're describing things that tend to be "one" thing (ie: a single resort) you probably don't need the taxonomies.
You might want to look at another option: PODS CMS http://podscms.com
This will give you a simple structure to add custom features to your posts relatively easily... Things like pricing, amenities, and other "organizable" details can be stored using PODS and then referenced across your site for better usability. It might be worth a look!
I have been looking all over for this, but so far without any luck. Is there a way to have comments per field instead of per node in drupal? If there are no modules available for this, do you think it would be hard to implement?
I thought I could make a "pseudo-content-type" with views that's nothing more than several content types displayed one on top of the other, so you could comment any of them. But then I don't know a way of making the user create all those content types at once.
The built-in comment module is not going to do comments per field on a node. I've been drupaling for almost three years and I don't know of any module that allows comments per field.
It is possible to do, but it would take a custom module and plenty of slick programming to get it to work. As far as difficulty I think an intermediate PHP developer with some knowledge of Drupal should be able to whip this out.
A kind of quick solution would be using panel module; form all your commentable content in nodes ad put them together all into a panel. This is kind a quick and static solution, possibly with views one can make it more custom.
I'm looking at these two modules for a "Related articles" style listing:
Similar by Terms
Similar Entries
Any opinions on either of them? I have a tag system set up so searching by terms would be fine, but it hasn't been updated as recently as the other module. How reliable is "Similar Entries"? Anyone have any field experience with either?
I would also take a look at Content recommendation modules wiki in the Similar Module Review on groups.drupal.org.
Looking at Comparison of Similiar / Relevant by term block modules, Similar By Terms seems preferable because
There is a version for Drupal 7.
It has been updated at the end of July (Similar Entries has been updated on May 2009).
It caches the results.
If I would have to choose a different module, I would choose Relevant Content, which has also a CCK field that allows you to put a list of related nodes in each nodes you want.