SugarCRM 6.5 how to customize custom module view page print layout - sugarcrm

I am beginner SugarCRM developer, I have create custom module successful and working fine. detailview page click print button, printing the different layout. How can I customize this?

SugarCRM has its own css for print media. You can check its ruls in theme style.css
Now if you want to add any further rules then you can do it following way:
#media print {
…
}
You will need to learn more about modifying print layout using CSS. This is something using SugarCRM itself(CSS for print layout). So either you can modify existing rules or can create new one. This link might help.

Related

How to set up a TypoScript Playground in Typo 3?

How can one play around with TypoScript code shown in documentations about TypoScript?
Tested with a local Typo3 test instance, Typo3 version 9.5.5, Official Introduction Package installed.
In the backend, create a new page in the tree. Rightclick -> enable it (the red overlay should disappear). Make sure it is selected in the tree.
Click on the blue Template button on the left. Usually it will show you the blue No Template message.
Make sure on the top Info/Modify is selected from the drop down.
Click the gray + (New record) button under the drop down.
On the bottom, click Edit the whole template record.
Optionally give it a speaking template and website title, like 'Playaround' and 'Play Around'.
Optionally, under tab Options -> Clear, select Constants and Setup - this will clear everything this Template has inherited from parent templates, but will also disable the debug infos at the bottom of the frontend for this page (if you have installed the Official Introduction Package).
Under the tab General -> text entry Setup, enter the following TypoScript:
page = PAGE
page.10 = TEXT
page.10.value = Hello World
press the Save and then the View button.
A new tab opens, showing you the frontend for your page, printing the text 'Hello World'.
Now you can play around with the code examples given in eg. the TypoScript Reference.
Funnily enough, I just found out that Typoscript is by definition not a programming language, but a configuration description. That's why Typo3 is needed as a substructure for this, I think. There seem to be online demos of Typo3 on the net, but I don't know whether they are up to date and whether you can test TypoScript there. Therefore access local containers / installations as suggested. Or if the possibility exists a dev subdomain.

How to add custom javascript in Laravel-Backpack

Is there any way to add custom javascript?
I want to add custom javascript to some of the pages but it seems i am not able to.
Each default Backpack operation has its own CSS and JS file, in:
public/vendor/backpack/crud/css
public/vendor/backpack/crud/js
If you don't find one there, you can create one, and Backpack will pick it up in that operation's view (e.g. create.css or list.js).
Read more: https://backpackforlaravel.com/docs/3.5/crud-how-to#customize-css-and-js-for-default-crud-operations

Breadcrumb doesn't work on a component I created (Joomla!)

I'm learning how to use Joomla! 3.2
I created a new component, then I added it to my main menu,
Here are the only parameters I changed in the main menu:
But now when I go to my new component the breadcrumb doesn't work correctly, there's only the home button and when I click on it I'm redirected to the same page:
Did i missed something very important? How can I fix it? The breadcrumb works on every other pages.
Ok I found the problem, I forgot to add this
$pathway = $app->getPathway();
$breadcrumb = $pathway->setPathway(array());
$pathway->addItem( JText::_( 'COM_PARTISPOLITIQUES' ),JRoute::_('index.php?option=com_partispolitiques&view=partispolitique'));
$pathway->addItem( "Current page name",'');
In the file view.html.php located in my component folder...
I am going to assume you are using the Helix template as it seems to be a common oversight.
Make sure that Enable Page Title is enabled from your menu Helix Page Title tab.
If not, please advise as to what template.

not able to register two plugins of touch-ui rte dialog

I am using the steps given in the URL to make a color-picker rte plugin
http://experience-aem.blogspot.in/2015/01/aem-6-sp1-touchui-richtext-editor-color-picker-plugin.html
and at the same time I am making another custom rte plugin to do some text modulation.
But only one of them is working using rte.coralui2 as categories.
and both icons are coming at the same location.
If I disable one js then another is working.
I have registered the plugin with different name and I have also used different variables.
I am not able to make the rte plugin button at different location.
Please suggest the possible solution.
it's possible you are overlaying rather than extending the rte.coralui2 category. I suspect your custom clientLibs are competing with each other and only one is available.
It seems like you are using the same steps provided in the blogpost for creating both the plugins and while doing that, you are using the below code twice with different icons :
if(items.indexOf(ExperienceAEM.TCP_UI_SETTING) == -1){
items.splice(3, 0, ExperienceAEM.TCP_UI_SETTING);
}
So, maybe, the icons are being added at the same place and only one of them is shown.
You should create ExperienceAEM.CuiToolbarBuilder Class only once and add both icons inside that class

how can we remove that Liferay Logo , Sign In Hyperlinkand Powered BY ?? from the screen

I am using Liferay 6 and Tomcat for development .
I have developed a Custom Login POrtlet for my Application
Now on entering http://localhost:8086 , my Custom Login Page is displayed .
Please see the screen shot .
My question is , could anybody tell me how can we remove that Liferay Logo , Sign In Hyperlink ( Extreme right top ) and Powered BY ?? from the screen .
Actually the Logo can be changed without creating a theme. The other items require a cusotm theme however (where you will want to edit the velocity macros). For the logo look under Control Panel > Portal > Portal Settings and then click "Display Settings" on the right side.
Additionally you can also provide a small amount of css to the basic theme as well, but this should be considered a temporary hack at best. Go to Manage > Page Layout > Public Pages and at the bottom you will see a section labled CSS in there you can do:
#sign-in { display: none }
.powered-by { display:none }
But bear in mind that a user with firebug or similar tools can still expose the old sign-in by changing the CSS in firebug and the Liferay tag line is still in the source so it's only hidden from non-technical folks. A theme is really the right solution.
Yes you can remove all of those by creating your own Liferay Theme, deploying it, and then setting that Theme as the one to use for your Community.
This Liferay Wiki Article on creating Theme's should get you started, if you have any questions after this then ask away! :)
Go to custom.css file inside _diff folder of your theme add the below code:
#sign-in { display: none }