Do hidden items get published? - sitecore

I am looking to find out whether or not Items that are either descendants of or are, themselves, hidden items get published when a user Publishes or Republishes the content tree.
I know that this is a pretty basic question, but I haven't been able to find the answer online, and I do not currently have an instance set up with additional roles and users, to use to test this.
Thanks for your help! Happy coding :)

Items which have Hidden field set to true are published as any other items.
Still remember that this is up to you what kind of access rights you'll set for them and who will be able to access them.

By hidden items - do you mean things like the /sitecore/System folder? In any case, as long as it's publishable (i.e. not in workflow, not set as unpublishable in publishing restrictions and the like), it will be published.
Edit
It is important to note that it's parent/ancestors should also be publishable, otherwise it'll still not be published.

All items get published unless marked as Never Publish or have Publish End Date set to earlier than today (In this case the already published items get unpublished/deleted from web database)

Related

Sitecore item:setdefaultworkflow and item:resetdefaultworkflow commands

I am Using Sitecore 6.6
I believe item:setdefaultworkflow and item:resetdefaultworkflow commands are used to reset the workflow fields on an Item with values set on Standard values.
If not please correct me.
Here is the Path in Core:
/sitecore/content/Applications/Content Editor/Ribbons/Chunks/Workflow/Set Default Workflow
commands are not shown on the Ribbon. How do I use these commands? what is their purpose. Any Help is greatly appreciated.
I am aware of Version >> Fields(Reset)>> then choose the fields to reset with multiple clicks.
I am trying to use these commands if they solve my purpose to reset the Workflow Fields to standard values with a command on Review Tab >> Workflow section with one Click.
As far as I'm aware, these buttons are only visible on __Standard Values items. They are used to assign the workflow that will be used for new versions of that template going forward, or to clear the workflow that has been set (note that items which are already part way through a workflow will still need to finish it before they are no longer associated with a workflow).
The idea is that you assign the workflow to the standard values of templates (or base templates) in your solution, and those settings then get carried through to your content items.
Although you are able to, I'd advise against fiddling with the workflow fields on individual items before you fully understand the purpose of the fields.
For more information, I'd suggest looking at the Sitecore workflow reference document: https://sdn.sitecore.net/upload/sitecore6/60/workflow_reference_sc60orlater-a4.pdf

Moodle Webservice API dont returns correctly

I am currently trying two methods of web service API (Moodle 2.6) to call with REST:
1 core_course_get_categories
2 core_course_create_courses
With both I have the following problems:
1
The function returns me categories back but unfortunately no subcategories. Even if I add like the documentation says the parameter "addsubcategories = 1", only the top-level Categories are sent back. An idea what the issue could be?
2
The course creation works so far, but I would like to assign the instructor to a specific user. Now when I create a course, it is indeed created under the users with the WS-rights. Is there a possibility to change the instructor?
Short background:
We have a central system where teachers can save new course information. Here should you have the opportunity to create a Moodle course immediately. We have in both systems a unique identifier of the user that should become the instructor. Of course, must be prior to the course, the Category / Subcategory be selected.
I would be happy about feedback!
This is a very late answer however I think it might be a valid solution to the first issue above and hopefully will help someone with similar issues.
A webservice user with the permission moodle/category:manage will be able to see all categories, hidden or visible as well as all levels of categories.
However there is no mention of this restriction in the Moodle API docs (that I could find at least).
Hope that helps anyone with this issue in the future.
Regards

Listing multiple Redmine issues by Id

I am working on some custom Redmine reports. In the generated report, there are numbers that represent things like "number of issues moved to Development during Q3 2013". The report generator knows the issue id of every issue that matches that criteria.
Is there a way to construct a Redmine URL that shows a list of all issues given a list of issue ids? For example, something like (this doesn't actually work):
http://redmine/projects/example/issues?ids=1234,1239,1245
This is similar to existing feature requests such as http://www.redmine.org/issues/10828 but I'm looking for the user-facing HTML version, not an API function. The idea is to allow the user viewing the report to click on the number and to see the corresponding list of issues.
The solution I ended up with was to include the list of issues in a <div> for each number in the report that the user could click on. Then, when the user clicks on a number, the corresponding <div> is displayed using a jQuery UI dialog.
This is not the same as using the Redmine issue list screen to show the issues. However, for this purpose it works well enough.
No, this is not implemented. But for me it should never be necessary in the Gui.
My Solution would be : Build the adequate query. Eventually this will need the addition of a field in Redmine and backporting the information from your tool to Redmine. Generally the need for this feature shows your bug tracker lacks some information that he should track.

Validate unpublished items and give a warning

Scenarion: Content Editor users keeps adding several articles, they can be in different places in the content tree. They want to know that which items has to be published by looking at validations in the content tree.
Can someone help me to write a validation rule to identify whether item is not published and give a warning saying "Item has not been published yet".
Thanks.
There's a module called the Published Item Comparer that might do what you need:
http://blog.velir.com/index.php/2011/04/29/published-item-comparer/
You could also consider using Workflow, and set the final approval step to also publish the item if you want. The user will be able to see what step of the workflow process the items are in the Workbox.

Sitecore item will not go into edit mode; any suggestions on how to troubleshoot?

I have several Sitecore items (whose template is connected to an approval workflow) that will not go into Edit mode when clicking "Edit" from the "Review" tab. The same workflow is used elsewhere on the site successfully (the site is more than 3 years old), but clicking Edit in this case doesn't seem to affect the workflow state.
I've turned on verbose logging, which provides a lot of detail, but nothing to indicate any error conditions. I've been comparing how this template is configured with other "working" templates for a couple of days and everything looks Kosher, but surely I'm missing something obvious.
EDIT: The item(s) in question are imported by a data provider, and I've confirmed that for some reason Sitecore is not setting the "Workflow" and "State" system standard fields with a default value. That appears to be at least part of the issue.
EDIT 2: Followed the steps in this thread http://sdn.sitecore.net/Forum/ShowPost.aspx?PostID=45991 to use Sitecore Rocks to update all of the items to the correct Workflow State, but the update did not stick. For some reason workflow changes are not persisted for imported items.
EDIT 3: Clicking the Edit dropdown button under the Home tab displays the message "The item is currently not part of a workflow."
Standard values set correctly? Only have one Standard Values item for this template?
Generally, almost every time I run into a situation where X works on certain items, but not on others... it's a permissions issue. You've tested this as an Administrator I hope?
Sorry my suggestions are so vague, but it's hard to be specific here. We need some more information from you... When you click on Edit what exactly are you expecting to happen? I'm not entirely sure what you mean by "Edit mode" here. In Content Editor, all items are essentially in edit mode all the time... In my configuration, when I click on Edit, I am just locking the item. It does not change workflow state or create a new version.
These items are coming from a data provider... is your data provider handling Lock/Unlock calls properly? I know it's possible to use a data provider without implementing the entire Item API.