I am searching for some solutions in Sugar CRM that will allow me to set default height for all the future dashlets to be created with increased height. Not just a single one.
Info:
Sugar version 12
Thanks
Related
I am trying to add a spotify music player to my website, a wordpress website. I tried with two different add-ons ,in one it was only available the widget player as a free option and the other one, give what I was looking for but I am not able to change the size of it.
The code is
[spotifyplaybutton play="spotify:album:6ttYxo44Qt6rC1z8ibKn9s" view=”coverart” size=”0″ sizetype=”compact” theme=”white”]
The only two sizetype available within the add-on is big or compact, in both cases I am getting the same size of the music player.
You can see how it looks like from the website, griotblues.com/music
Follow the approach mentioned here
You can specify the height and width of the player by setting the height and width properties of the iframe
Does anybody know what is the difference between Installed & Hidden properties of WKInterfaceLabel ?
Both of them show/hide the label .
For WatchKit apps, all interface elements required in an app scene have to be created in the storyboard in Xcode and installed with the app... they cannot be added programatically at runtime. The hidden attribute sets whether an element is hidden or visible at launch. This can be subsequently changed programatically, and so toggling the hidden attribute is used in a manner akin to adding or removing items from a view in iOS.
The installed attribute sets whether an interface element is installed at all in the Watch App when it is copied to the Watch. If an item is not installed, it cannot be used.
A principal way in which you might use this installed attribute is to have different interface elements on different sizes of Apple Watch. By clicking the + to the left of the Installed checkbox in Xcode, you have the option to set different values of this attribute for different Apple Watch sizes.
Having selected a Watch size, you can then set different values for that watch size compared to the default size:
These changes can also be made by selecting the Apple Watch size at the bottom of the interface builder window, and making the changes directly on the storyboard. These are simply two paths to make exactly the same changes, rather than actual different alternative solutions.
Note that Apple recommend that Watch app interfaces should as much as possible be the same across all Apple Watches, with interface elements varying only in size. It is possible to make these size changes for many interface elements using size constraints that set the size relative to the element's container. However, for buttons with images this is a method for installing buttons with images sized specifically for each watch.
Check WKInterfaceObject Class Reference
Installed: A checkbox indicating whether the item is installed for the
current device.
Here is the JS Fiddle:
http://jsfiddle.net/3E8nk/362/
For some reason I cannot seem to get the eventLimit property to work correctly, or at all in fact. Now it states in the documentation that:
A value of true will limit the number of events to the height of the day cell.
However I cannot see how to set the height of the day cells either. There are height properties for the header, and the calender body but the does not seem to affect the individual day cells.
What's annoying me is that on the front page of the fullcalendar website (http://arshaw.com/fullcalendar/) It seems to work fine, without setting any height variables at all simply just eventLimit: 'true'.
Can anyone shed some light on this?
You are using FullCalendar 2.0.0 and the demo page is using FullCalendar 2.1.0.
If you check this blog post describing the changes for the version 2.1.0 (which was released today), you will see that what you need was released on this version.
So, you only need to update the Javascript and CSS and that will work.
In Plone the default folder_contents etc. views display 20 items per page. This is too small number for most of our use cases. How to increase this number to 100?
See https://dev.plone.org/ticket/8115:
The number of items shown by default in the foldercontents is hardcoded in a BrowserView: tableview.py. Although I think it's a good default, I find it frustratingly small for some of my websites. I would suggest to move this value to a new property in site_properties.
You'll have to edit tableview.py, I think.
i'm currently having a nightmarish moment with Sitecore. Basically my issues are two-fold:
1) the first time i added a standard value item to a template, and added a layout setup to it, i was thrilled, since all my items from that template were showing the layout, however now, certain items are now showing no layout at all. I tried doing presentation->layout, reset several times, but to no avail.
2) i added a new sublayout to the standard value layout to another placeholder, did publish on the template (republish everything, publish subitems), then publish on the standard values item again, just in case (should not be needed), i click on all items from the template, and they show the updated layout with the new sublayout (should be good, right?) however, i browse, both live and with preview to the pages and i am still seeing the old layout without my new sublayout.
- I added a breakpoint in the page_load of the new sublayout but it never hits, the others do
- I tried cleaning the cache on sitecore/admin/cache.aspx, but did not help
- tried recycling the app pool, restarting the web site, spreading black rooster' blood over the machine, nothing seems to helps
i am using sitecore 6.2.0 (rev. 100701), visual studio 2008 SP1, IIS7 in integrated mode
Basically the way to do it is set layout on the Standard Values, which should update all items, that haven't had their layout overwritten on the item or by a branch.
This is the key to the issue. If your items that aren't getting updated with the template standard value layout were created using a branch, check to make sure that branch does not also have layout details associated with it. If the branch has layout details in addition to the template, the two will conflict and cause really odd, frustrating behavior.
I encountered the exact same scenario, but after removing the layout details from my branch the issue went away.
Sounds strange... usually this only happens, when you have a "conflict" between layout set on Standard Values, template/branch.
Basically the way to do it is set layout on the Standard Values, which should update all items, that haven't had their layout overwritten on the item or by a branch.
I really dislike branches, so always try to avoid them (the only real use when they were Masters were for building hierarchies of items).
Could you try to look in the __layouts field (View > Raw values) of the items and see if anything is entered there?
And is it only some items or all items based on that template?