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.
Related
Is there a way to make the language property list shorter? Make it show only EN-US and PT-BR, for instance, so it's easier to find them?
You probably don't need to do it.. You can likely just make your life easier like:
Make a new form, lets say it's called LocalForm.vb
Drop a label on it, lets say called HelloLabel
Set form to de-DE, set the text of the label to Hallo
Set form to fr-FR, set the text of the label to Salut
Set the form back to (default) - you now have LocalForm.resx, LocalForm.de-DE.resx and LocalForm.fr-FR.resx and you can add controls
Add a Button, called StartButton
Double click the LocalForm.de-DE.resx file
Dismiss the "if you mess this up you'll have to fix it yourself" dialog
Add a line for StartButton.Text Starten
Repeat for other language files
Dropping a control named XyzButton on the form, and then visiting each LocalFor.*.resx in turn and adding the locale for it is a lot easier than back-and-forthing with the language setting, though I know why it's done the way MS chose to do it - you're supposed to lay your form out perfectly with all its hundreds of controls, and then switch to French and write all the French for all hundreds controls, and then switch to German and write it all in German.. In a use case like that there isn't a lot of work to do with that awkwardly huge Language dropdown. Incremental adds that way are a bit of a pain..
Perhaps raise a connect bug/feature asking them to put the "already used" languages (as determined by the presence of Form.*.resx files) at the top of the list, and wait many years for it to be implemented :)
Note: There's a bit of a nuisance with this "edit the resx" in that if you rename a control it doesn't always get picked up. Last time I was localizing I threw together an app that watched (FileSystemWatcher) files named *Form.resx and if it saw a change (load the current version, compare to the prev version) that was a rename, it made the same change in the other files (or maybe alerted if they weren't in sync.. can't quite remember now and I've no idea where the code has gone)
Maybe don't rename your controls after you first decide a sensible name for them/add them to the translated resx..
Please how can i change text and links in the highlited zones in the picture below :
Click to see
Thanx a lot
Prestashop comes with a translation mechanism. Usually from your Prestashop backend, navigate to Localization > Translation, then identify "Modify Translations ". Select the type of translation, the theme and the language and hit on the button "Modify" on the right hand side. Look for any module in the front office translations group that contains "search".
Your situation may be a little be different because you are not using the default theme. You theme developer has probably created a new quick search module. You would need to identify the actual module and it should be easy to identify it from the list of translatable module. If the module is not well developed, it will not be possible to modify them. In that case, you should ask your theme developer.
I hope it help. Good luck with your business.
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/
I've a question. I cannot find the way, how to add buttons to main toolbar programmatically. My problem is, that I've the task to dynamically (based on XML configuration file) build menus and toolbar. I found how to add a menu item programmatically, but not toolbar button.
Tutorials mostly show how to create buttons and menus using plugin descriptor (plugin.xml), but not how to do it programatically. It seems, that it is out of bounds of Eclipse plugin philosophy.
I've just found this:
There might be layout problems with this approach. I also don't
believe the framework will try and re-create your dynamic item except
at random toolbarmanager updates. With Menus they can be updated on an
SWT.Show event, which is why CompoundContributionItem only applies to
Menus.
What shall I do? Can I say Sorry, there is no way to build toolbar dynamically. I can do it just for menus? Collegue says, that it must be possible, but he does neither know how.
The only way to be able to create main toolbar entries programmatically is in an RCP app, where you supply the ActionBarAdvisor for the workbench window. This isn't dynamic, however, just called on window creation.
Another way to do it would be to use org.eclipse.ui.menus and contribute org.eclipse.ui.menus.ExtensionContributionFactory. It also works only on workbench window creation (not really dynamic), but you could read your own XML and provide IContributionItems for the main menu or toolbar.
How dynamic are you trying to be? Most solutions work well on startup/window creation.
PW
Whenever you try to do something programmatically in Eclipse that is normally done through plugin definitions you are walking on thin ice. I've tried it on a few occasions and it rarely ended up being easy or good.
Instead, think of what it is that you only know at runtime and need to be able to change on the fly. Is it the name or icon of the button? That can be changed at runtime.
Take a look at runtime commands, they can be confusing to define properly, but with them you can for example create buttons that are only visible if a condition is active. That condition could be set at runtime.
On the compile tab of the project properties:
If you look at the configuration dropdown it typically shows debug/release/active/all.
I attempted to add another option at one point in the build->configuration manager window, but decided that I didn't want to keep it. I removed it there, but it keeps showing up in the dropdown on the properties, as well as generates a folder by that name.
Does anyone know how to remove this? I can't find any "delete" or otherwise options.
You likely just removed it at one level. Check the configuration manager on your Solution, and then on each of the projects within the Solution, and make sure it's removed from each.
(By going to the drop down, clicking , then remove just as you did before)