According to the TYPO3 manual:
Where is the Alias field?
Alias field in TYPO3 page properties The Alias field can be found in
the page properties. Here it is located on the so-called "second
options palette", which is not visible by default. To show this
palette, you need to check the "Show secondary options (palettes)"
checkbox at the bottom of the page properites form.
In recent TYPO3 versions (eg.. 4.5.2) the Alias field is located in
the page properties, tab "Behaviour" and is called "URL Alias".
Here's a screenshot from the page properties how I see them:
But where is the "Alias" field in the version we are using? (TYPO3 Ver. 4.5.19).
Even if I put the Type of the page to "Advanced" instead of "Standard". I get a lot more tabs, but not the "Behaviour" tab. In the access list of the user group, everything is checked and the user has full admin rights.
Your properties form on the screenshot lacks many common fields and tabs, apparently you logged in as a common admin without access to it. (see typical form (4.6.x) for compression)
Log in as a full admin and check if these fields are available.
If not that means, they where disabled with PageTS/UserTS
If they are available for full admin and you need/want to enable them for common editors as well you need edit access lists of the editor's group and by selecting proper Allowed excludefields
It might also be worth noticing that there is a difference between the "Live" and "Draft" workspace. It may not show up in the Draft workspace whereas it does show in the Live workspace. Just noticed this recently.
Related
On JIRA tickets I can format comments entries at will : there's a toolbar with many choices for that, color, styles, underline...
But how do I get the same for description field ("descriptif" in French)?
Because what people read for explanation of a story/task/ticket, is mainly this content.
And currently the only thing we can do is to write on some descriptions "Look at comments to learn the purpose of this item/understand something" because a plain text is sometimes not enough to explain things.
This can be handled with renderers under Field Configuration Scheme.
Open Project settings -> Field Configuration.
Find the field "Descriptif"
There should be a text called "Renderers", click that. (In some version, it may be inside Edit)
Select "Wiki-style Renderer"
Click "Update" button.
And voila, it should be formatted like the Comment field.
Also, for further info you can check following Atlassian documentation.
For a custom language I created a CompletionContributor. Everything works fine. But I'm limited to the information I can display (only in the list or the bottom "advertisement" and only 1 line).
When trying to auto-complete on a java class name it will display more information on the selected line in a small side window. I would like to exploit that mechanism but I really don't know how it is done.
When looking at the options provided, I can use a custom LookupElementRenderer but there is no method in LookupElementPresentation related to the right window.
Any idea how it is done?
Are you referring to documentation popup which may be displayed if the corresponding setting (Setting->Editor->General->Code completion->Show the documentation popup in) is turned on?
If you want the feature to work for your language you have to use lang.documentationProvider extension point.
Ektron 9 - steps to trigger issue ... we think:
Create new content folder
Edit folder properties
Smart Forms tab - untick inherit, and remove "Blank HTML"
The "new" menu on the folder now:
Does not show DMS Document as a menu item
Does not show Smart Form list as a pull-out sub menu.
Question
How do I get "Blank HTML" back into the smart form tab property in the folder
Why is this happening
Help!!
[Edited] Workaround
eGandalf gave the simple answer via Twitter (previously I had attempted a workaround of putting inheritance back on then resetting the tree): toggle the "Require Smart Forms" checkbox on the "Smart Forms" tab and the Blank HTML option will come back.
This is by design. When you remove the HTML option, note that it checks the "Require Smart Form" box (and, reciprocally, checking the Require Smart Form box removes the HTML option). That means that all other types, including PageBuilder, DMS documents, or HTML are now forbidden in this folder.
As a best practice, you shouldn't be mixing types in a folder anyway. A lot of people do, but that doesn't make it any more valid. If you've got a folder for Press Releases and you have a Press Release Smart Form, you shouldn't have any other type of content in that folder. The less you mix types, the less filtering you have to do either with the API or post-request via LINQ. As a result, you'll have a more consistently performing site.
In situations like this, where I want the DMS assets and the Smart Form content to a) both be searchable, b) both be managed by the same user/group and c) there's a strong connection between the two (e.g., Whitepaper information Smart Form + PDF asset download), I'll create a child folder and allow DMS assets there. In the Case Study example, the folder structure may look like this:
Content
Case Studies (Smart Form only)
Downloads (DMS Allowed)
In contrast, if I don't want the DMS assets to be independently searchable, I'll remove them from the Content folder entirely and place them in a separate, root-level, non-searchable folder called Resources or Downloads.
Because Blank HTML is a default (and ID 0), you might have to reassign it in the database.
My guess is that removing the Blank HTML option impacts DMS retrieval in the workarea specifically.
In this case, I'd reach out to support, I've never actually needed/wanted to do this.
Edit:
I dug a bit more to try and give you something to try.
You'll need to reinsert an xml_id into folder_to_xml_tbl.
insert into folder_to_xml_tbl VALUES(your_folder_id, 0, 1);
Ektron support have replied:
Hi ,
Engineering have advised that DMS documents are unstructured.
By forcing all content to be structured content, it disallows raw html as well as dms assets and only allows documents with structure to be created
In any reply please include the case number in the subject line.
To open a new case email uksupport#ektron.com or use the support request form at http://www.ektron.com/Resources/Support/Contact/
How can I change a URL in joomla from :
http://sitename.com/components/original-component-name/rest
To:
http://sitename.com/components/any-component-alias/rest
While what you are asking to do is possible, it would be rather complicated to rename a component. As part of the renaming you would have to update the names of dozens if not hundreds of classes throughout every file of the component. Very likely to run into some bugs because of this.
The far easier prospect is to just avoid these types of urls in your site. Joomla will only fall back to that style of url if a menu item does not exist for the view. Because of that, you can make the url into this:
http://sitename.com/any-component-alias/
To do this, go into the menu manager and create a new menu item. If you don't want this as part of the main menu, you can create a new menu. (I typically have a menu called "Hidden" for menu items that I want aliased but don't actually link to throughout the site from a menu.) When creating the menu item, make sure the type matches the component and view. The alias will then be whatever is entered in the alias box just below the title.
The one issue you may run into with this is that a component may not have a menu type for a particular view. In that case, you you would need to add the necessary metadata.xml file to the view (which again would be much easier than renaming the component!). A good tutorial for that can be found here: http://docs.joomla.org/Adding_view_layout_configuration_parameters.
I am working on a solution to allow users to search for other users, since we use SharePoint 2010 and have access to the SharePoint people search it seems like an easy solution. For the most part it is close to what is needed but it appears to be missing a few things.
The biggest thing is the ability to search by office/location.
The search appears to return the office location but I can't seem to search on it.
I expected to be able to search on it by doing BaseOfficeLocation:"Office Location To Search For" since Department:"Department To Search for" appears to work.
I have tried Office and OfficeLocation but it just doesn't seem to work. I found a blog that said that it appeared as if this didn't work as expected but there were no more details.
Is there a setting that I need to enable or do I need to do some custom development here?
This might be a little late but here goes.
You basically need to add a metadata property that maps to the office (or whatever) field on the users profile. You then need to have that crawled. Finally you can add office to the search option. Below give you a quick overview of how to do it.
Adding a new managed metadata property
Go to Central Admin.
Go to manage service applications
Go into your search service application
On the left under "Queries and Results" go to "Managed Metadata Properties"
Click "New Managed Property"
Give it a name, I called mine "Office"
Click "add mapping" and select people
Select "People:Office(Text)" (this depends on which field on the profile you are using to put the office in)
Select "Include values from a single crawled property based on the order specified"
Click OK
Now run A FULL CRAWL. That's quite important. If it's not a full crawl it wont be picked up.
Wait for the full crawl to finish.
Adding the field to the search
You should now be able to search for Office:"office name"
That's not very useful to a user
What we want is to add it to the search options
Edit the page and go to the web part properties for the search box
Go to "Miscellaneous" and expand it
Open up "Properties" and copy out the XML. Here you now need to add in your new field.
It's going to look something like this:
<Property Name="Office" ManagedName="Office" ProfileURI="urn:schemas-microsoft-com:sharepoint:portal:profile:Office"/>
Add that in and then save it back into the web part
Click on search option, type in the office in the new office field and click search
BOOM!! Office searching.
Unless I'm missing something you're going to need to do this on both the initial people search page and the results page.
Here's a link that i based that all on.
http://blogs.technet.com/b/meamcs/archive/2010/12/23/sharepoint-2010-people-search-using-metadata.aspx