Is possible to hide or disable some actions in Page Explorer for certain Page type?
For example, when the page type is "Página Externa" I want not show Move, Copy and Revisions actions.
Related
Is it possible to add custom pages in the admin sidebar and remove the "Pages" link. I want to have different links such as:
Blog Posts
Pages
Events
Games
Shown in the sidebar and each listing page only shows items based on the custom page. I have been looking in the documentation and the only thing that I found was to add custom URLs to the sidebar but I need to also add custom pages to show listings.
The ModelAdmin module allows you to register page models to appear as new items in the admin menu.
You can add exclude_from_explorer = True to your ModelAdmin definition to hide a page type from the main page explorer, although that won't hide the Pages menu item itself - for that, you would need to define a construct_main_menu hook to run after the menu has been built, and remove it from the list.
On standard salesforce page, I need to display some custom buttons based on some conditions. The decision to display the button or not is based on response from Apex method. As my page is standard visual force page, how can I trigger the JavaScript function before the page is loaded so that I can take a decision whether to display the button or not?
You can display a custom button on standard salesforce page. but salesforce not allowed to make any call on load of standard page. Salesforce have a feature that is page layout. You can create different record type with page layout in that you can use custom button as your need.
On the other hand you can make a decision and filter when javascript custom button click and show error like 'you are not allowed to click this button'.
How can a user that have Developer Account can add custom button to a standard page is there a way to do that. Because I couldn't find editing a button, adding a button or editing button's redirect URL for a standart visualforce edit page. i.e Opportunity creation form.
Your question is unclear :/
Your organisation is a "Developer Edition" (a free one to try out working on Force.com platform) or for example "Enterprise Edition" and your user Profile (a set of system permissions) is called "Developer"? In "Developer Edition" you probably are a System Administrator, so you have all the rights. In the later case - check if your profile has "Customize Application" permission for a start.
What do you mean by "standard visualforce edit page", there's no such thing. You mean standard page layout or do you have custom Visualforce Page that's used to edit opportunities?
Best guess answer:
You can go to Setup -> Customize -> Opportunities -> Buttons and Links, create there a "Detail Page Button" and when it's done - add it to the page layout(s) of Opportunities. If you don't see these options - you don't have permission to customize application.
BUT: none of the buttons added that way can be displayed on the "edit" page, which is a standard one with very limited customisation options. Only standard "view" page displays the extra buttons. There are some JavaScript tricks to inject content to "new/edit" (via section headers or sidebar)... But if you want the button to behave reliably best might be
to make a Visualforce page and override the actions.
What exactly this button should do?
You can not delete the standard button but you can edit it and override it with Visualforce page. You can find the all standard buttons for the opportunity are here. Setup-->App Setup --> Customize --> Opportunity --> Buttons and Links.
Form here you can either create any custom button or you can edit the standard button.
Note : If you are overriding standard page with Visualforce page then make sure that the Visualforce page is having standardcontroller as selected object i.e. here in this case is "Opportunity"
To add a custom button to a standard page go to Setup -> Customize -> Opportunity -> Buttons & Links. Click "New" custom button and link button.
Here is a good tutorial for adding javascript actions.
http://www.interactiveties.com/b_execute_javascript_button.php
If you wanted to override standard buttons with visualforce pages, create your page first, then on the same buttons and link page from above, select "Edit" on the action you want to override.
I'm running a dotnetnuke project (v7.0) with 2 portals.
I need to remove the default DDR menu from one page only.
The menu works great now with multiple pages and sub-pages, however on 1 specific page , ie landing page, I don't want to show the menu.
Right now I can think of 2 methods for achieving this:
Create a new skin template, remove menu, apply template to that one page
Use jquery to detect URL, for that page hide menu.
I'd rather just code the logic inside the template file, but I'm not strong in .net/c# and I'm new to DNN.
It's just one page today.
However, if you are using it for a landing page design I would recommend you just create another skin and exclude it from that and tailor that skin for that need.
That way when your non-technical editors need to work on the site and make a page that might only be used when linking from Google Adwords or whatever they can pick a template without that navigation and you as the developer/designer don't need to edit the skin to put in another exception based on the URL.
A regression in DotNetNuke 6 is that, by default, the editor appears in an in-page popup that uses a very limited portion of the screen.
While the editor does include the ability to go "full screen", this is not the default.
Is there a setting some place that I can adjust to cause it to always start full screen, or at least start out larger so that I don't have to scroll down to hit the save button?
One method for getting rid of this limited in-screen popup is to disable popups site-wide in the site settings (admin menu).
This will cause a full page load when the edit content button is clicked. The editing will be perform on a self-contained page. Clicking save will return the editor back to the page whose module is being edited.
Warning - Using this option will cause bulleted lists to not display as bulleted lists in design view within the default html editor