How to hide Resources tab on page translations in TYPO3 6.2 - typo3

How can i hide the BE tab "Resources" in translated page properties?
In TYPO3 6.2 i want to use the same media resources in page properties for all languages.
Frontend is done with:
$TYPO3_CONF_VARS[’FE’][’pageOverlayFields’] = ‘uid,title,subtitle,nav_title,keywords,description,abstract,author,author_email’;
(removed "media")
So any changes on the tab resources in page properties translations are ignored in FE. To avoid confused editors i want to hide this tab but i don't know how to do this.
(maybe it would be better to show the tab and the original language resources without the buttons "Add new relation" and "Select & upload files" but this sounds more complicated to me)
thanks for help

Related

How to open a popup on click of button placed in menu page in master detail page in xamarin forms?

I am working on xamarin.forms. I am using Master detail page. In menupage of MasterDetailPage I have some menu items that are listed. At the bottom of the Menu list I placed a button on menu page. Now I need to open a popup on click of that button. I am trying with PopupLayout but not able to get any success.
Please tell me how I can open a custom popup box at the click of the button that is placed in menu page?
Regards,
Anand Dubey
Without going into separate, native projects for all platforms you are targeting (such as Android, iOS, UWP...), you cannot pop out custom UI content over existing pages in Xamarin.Forms out of the box. You would need to bring in additional references or get creative with the AbsoluteLayout control.
Here are a few options you have:
Simple popup with message and or option selection
If all you need is a simple popup message or a list of buttons, you should look into the native DisplayAlert and DisplayActionSheet methods. They are built into Xamarin.Forms and work really well for these simple cases.
More complex popup dialogs
For anything more complex than that, there is the excellent UserDialogs project: ACR UserDialogs github page
It will give you support for various loading dialogs, date, time pickers, action sheet, success/info/error toasts and more.
Fully custom UI markup with AbsoluteLayout
There is a technique where by you prepare the underlying page with a root absoltue layout, which enables you to dynamically add new UI on top of all other controls on your page. This is fiddly and can ruin your performance if you are not careful. This is also the approach that the PopupLayout control that you mentioned uses. If done properly, this can be a good solution, but I don't recommend it as it involves additional complexity on each page that hosts the popup content.
Fully custom UI popup on native projects
Your most flexible option, as always, is to fall back to the native projects. This would involve coding up the popup logic on each separate platform that you are targeting, then using DependencyService (or one of the other techniques) to call into it from the shared project. For this you should look at samples and tutorials for popups on separate native platforms as it gets pretty broad and goes way outside the topic of this question.

Drupal 8 - browser tab title translations for views

I am creating a multilingual site in Drupal 8. The browser tab title for nodes translate, but in a view the titles are all in english.
Currently, the goal is to create one view page and use a URL alias to direct to the other translation views. I have the filter set to content revisions for languages using the "Interface text language selected for page". On these view pages, everything but the title translates.
Is there a way to force the browser tab titles to translate without having to create additional view pages for each language?
Thank you in advance for any advice
If by "browser tab title" you mean Views' title, enable "Configuration Translation" core module, and then click on "Translate" link next to your View ("Operations" column, /admin/structure/views).
If you mean titles of nodes' which you output in a View, then check out settings of a default prebuild "FrontPage" View, because it works just great with content translations, maybe you've just missed some important settings which you can spot there.

Rename Prestashop mobile menu caption

I use PrestaShop 1.6.0.9. I know how to change the items in the top navigation menu or how to add/delete categories from the left menu.
But I can't investigate how to change the caption of category menu in mobile template?
You can see here that the left category menu on desktop is called "Produkty". If you scale down the tab or you view it on your mobile, it is called "Menu". I would like to rename it. I tried to find it in the Localization / Translation of the template, core and moduls. Unfortunatelly without any success.
Do you know which files should be edited to display "Menu" caption as "Produkty" even on the mobile?
I finally figured it out.
It was located in files in www/modules/tmleftmenu/ and need to be replaced in in files:
tmleftmenu.tpl (for mobile view)
tmleftmenu_left.tpl (for desktop
view)

What is the difference between disable a page and hide the page in the meu into Typo3 CMS?

I am pretty new in Typo3 world (I came from Joomla and WordPress) and I have a doubt related to well understand what is the difference between disable a page and hide the page in the menu in Typo3.
I have create a new test page and I don't want that now it appears in my left main menu.
So I click on the Access tab of this page settings and I tick the Hide (In Menus) "checkbox" so the page exist (I can access and see it using its URL) but don't appear in my main menu.
This is pretty simple but, near to the previous options, I also find the Disable (Page) checkbox. So I have try to tick this checkbox (instead of Hide (In Menus)) and happens something that I did not expect:
My test page appear again in my left main menu (I have no hide it but if I thought that if I disable a page, it is as if this page does not exist, evidently the typo3 operating logic is different from what I expect)
If, in my left main menu, I click on my test page link: the page is open but on the right top corner on the page appear to me the following textual message PREVIEW!
What it mean? I am logged as administrator, maybe the normal visitor can't see the disabled pages whereas administrator\editor see these pages? Or what?
Tnx
Andrea
Disable page = Nobody can see the page. The page is removed from the menu and it can't be accessed with the URL. You see it because you're logged into the backend. That is also why you see the red sticker 'Preview', because it is a preview.
Hide in menu = Page is hidden from the menu and the sitemap, however, it can be accessed with the URL.
Check the following documentation:
http://docs.typo3.org/typo3cms/GettingStartedTutorial/
There is a very short mapping between TYPO3 and Joomla:
TYPO3 "disable" = Joomla "Unpublish Article"
TYPO3 "hide" = Joomla "Unpublish Menu Item"
Cheers,
S.

Wordpress - Show Portfolio Categories

I'm working with a WordPress website and a client wants to show a list of categories in the footer. Unfortunately, it is showing as empty because he has no posts and has set the categories to portfolio items which he wants people to be able to click to.
So, how do I show the portfolio categories in the widget rather than the post categories?
Thanks,
Jack
Probably the easiest way I can think of to get the result that you want without having to resort to changing any Theme Files would be this:
Log into your Wordpress Dashboard
Navigate to Appearance->Menus
Create a new Menu, and (if applicable) enable the Custom Taxonomies for your menu by clicking on Screen Options (top right-hand corner of the page) and ticking your Portfolio's Custom Categories and/or Custom Post Types
Once all of the items you want is in your Custom Menu, save it.
Navigate to Appearance->Widgets
Add the Custom Menu Widget to the sidebar in which you would like your items to appear
Select the Custom Menu you just created, and Save
When dealing with Premium Themes, it would always be safest to stay out of their code and avoid changing anything altogether, so try this approach first. Otherwise, you may have to get your hands dirty and alter some code or contact the Theme Developer.