I'm learning odoo 10 development with odooclass and I am blocked at the submenu creation step. Here my piece of code from the addon views.xml:
<record model="ir.actions.act_window" id="dmsapp.action_window_vehicles" >
<field name="name">Vehicles</field>
<field name="res_model">dmsapp.vehicle</field>
<field name="view_mode">tree,form</field>
</record>
<menuitem name="Vehicles" id="dmsapp.menu_vehicles" parent="sales_team.menu_sales"
action="dmsapp.action_window_vehicles"/>
The menu never appears but I can see it in the list of all sales menu items (developper>parameters>UI>menu) near product, customers, quotation...
I had rerun odoo, refresh web browser, clear cach and cookies, try to put groups acess, change sequence but the menu never appears.
I am logged as Administrator.
Thanks for help.
try change this parent="sales_team.menu_sales"
into this
parent="sales_team.menu_base_partner"
hope this help
I remove Shan Abdiel and vijay suggestions, rerun and it appears now. It's really a mystery. Does odoo-bin keep a sort of cache of generated html or other trick tike that? Is there a way to fully clear it?
Is it possible that this problem come with liclipse ? I notice that I remove all terminal launches before it worked. But I already did that yesterday...
Give access right of showing menu of Sales Team from res_users and rerun again.
This probably solves odoo caching problem: update your module/app. If it doesn't work uninstall and reinstall it.
Related
I'm tryng to use the tag cloud control from Ext.Library 9.0.1 (20160428). The cloud is generated with the correct values form the category view but all the links are missing.
I suspect I'm missing something stupid and my question will look a little bit silly but... I've already lost some hours on this without getting any result.
This is the code for the tagcloud:
<xe:tagCloud id="tagCloud1" sliderVisible="true">
<xe:this.cloudData>
<xe:dominoViewCloudData categoryColumn="0" viewName="indice"LinkTargetPage="/risultati.xsp" linkRequestParam="nometag">
</xe:dominoViewCloudData>
</xe:this.cloudData>
</xe:tagCloud>
This is what I get in a browser (just an example, all the lines look similar):
<li style="display:inline">
<a role="link" title="11 Entries" class="tagCloudSize9">Miscellaneous</a>
</li>
As you can see there is no link to anything, so the user can't click the cloud label.
Any advice will be appreciated
Thanks in advance
It seems it was only a cache-related trouble. I've restarted my server and it started to work as expected.
Just wondering why and how to avoid in the future...
Just getting the Google Glass GDK (19) running with Eclipse Java and its all up and running fine. ADB etc all good.
And now experimenting with the Compass Sample code. One thing I would like to try and pin down is basically customising whats there - a simple thing being the Touch Menu text which is "Show A Compass".
Can that be changed? That's all I want to do! However, strings.xml alters app_name only and the XML Trigger def of SHOW_A_COMPASS seems locked down somewhere. I guess that's what I am trying to discover.
Any pointers appreciated.
Thanks
Doug
You specify the trigger command in an XML file in your resources. In compass this is res/xml/compass_show.xml. In there, you will see a <trigger> tag, which you should change to one of the constants in VoiceTriggers.Command. So if you wanted to use the voice command "Find a product" you could use something like
<?xml version="1.0" encoding="utf-8"?>
<trigger command="FIND_A_PRODUCT" />
You can use your own voice commands... but only for testing purposes. Glassware that is reviewed and distributed through MyGlass must use a defined command. (You can, however, request a voice command be included in a future Glass update. If you plan to do this, you should request it as early as possible.)
See https://developers.google.com/glass/develop/gdk/voice for the full details.
I have a breakline problem using sendmail activity in a Sharepoint VS workflow.
I use < br/ > for the breakline, everything is ok in live mail&outlook but when i try it in lotus note all my text is inline.
How can i fix this problem ?
Hate to say it, but you probably can't 'fix' the problem. It sounds like just an HTML rendering bug in Lotus Notes. It doesn't sound like you're doing anything wrong in your HTML if it renders OK in other clients.
You might try changing your HTML code to find something that looks satisfactory in all clients, though. Perhaps add a second <BR /> or use a <P> instead?
Please, someone tell me if there is a replacement for the rubbish Solpart menu, the menu with the small arrow to administer a module in DotNetNuke?
I have been using DNN for some time now and I would love to know if there is not a better way to get this menu working. I cannot believe DNN would let something as buggy as that out!
Thanks
You can use any menu for that drop down. You'd just swap out the solpartmenu for the one you want in the container you create. Here is a blog post outlining some of the menu options available. I'd suggest taking a look into each one of these and see which would be a good fit for you.
New Navigation Options in DotNetNuke 5.x Designers Should Know
Below is one (slightly updated) example from How to use RadMenu instead of the default solpartactions menu
Open an existing container for edit (a Default DNN container will work fine).
Register the RADMENUACTIONS tag by adding the following line of code: <%# Register TagPrefix="dnn" TagName="RADMENUACTIONS" Src="~/DesktopModules/RadMenu/RadMenuActions.ascx" %>
Replace <dnn:ACTIONS ... /> with <dnn:RADMENUACTIONS ... />
Set additional properties for RadMenu if desired. For example you can set the Skin property: <dnn:RADMENUACTIONS runat="server" id="dnnRADMENUACTIONS" Skin="CssGreen" />
I'm creating some pages using a SiteDefinition, the markup looks something like this:
<File Url="Page.aspx" Name="$Resources:SiteDefinitions,PageName;" Type="GhostableInLibrary">
<Property Name="Title" Value="$Resources:SiteDefinitions,PageTitle;" />
<Property Name="PublishingPageLayout" Value="~SiteCollection/_catalogs/masterpage/Somepage.aspx"></Property>
<AllUsersWebPart WebPartZoneID="WebPartZone1" WebPartOrder="1">
-- webpart data here
</AllUsersWebPart>
</File>
The page is created as expected, but it's somewhat faulty. If for instance I click Edit Page and then click Publish (without actually editing anything) I will get this error:
"This Page has been modified since you opened it. You must open the page again."
I will get this error approx. every second time I try an editing action.
If I manually create a page using the same page layout everything works as expected and this error does not show up.
Does anybody have an idea what could be wrong?
I too create a Page using the above method only thing I found missing in your code is that I used to have a title in the PageLayout as
<Property Name="PublishingPageLayout" Value="~SiteCollection/_catalogs/masterpage/Somepage.aspx, Your title"></Property>
This should not be the cause, but you can try it, Also refer the articles this or this
I think you're right with using PublishingLayoutPage. I came across this article today while searching for this error caused by something else. It describes your same issue although the person in the article was not inheriting from PublishingLayoutPage and had not specified the PublishingPageLayout property. When they fixed this it worked.
This doesn't directly help you, although I did notice in their article that they are specifying the ContentType property. Have you tried specifying this? As you can see your complete code, are there any other differences you see from the article or additional information from the comments?
Okay, I (kinda) got this working now.
The guy who had made the ONET.xml had put a reference to the page layout in the Url attribute of the element.
Like I wrote in a comment earlier I tried making the page layouts inherit from TemplateRedirectionPage. Instead I now made an empty default.aspx file that inherits from TemplateRedirectionPage and changed all my page layout files back to deriving from the PublishingLayoutPage. And then I added the PublishingPageLayout element below every element.
Funny, or oddly, having a refence to the page layout in the Url attribute and not having the PublishingPageLayout element at all is actually valid. It doesn't make sense, because it will produce these faulty pages, but SharePoint actually accepts it and spits out all the pages defined in the ONET.xml
Only thing left now is that since I made the above changes, when I manually create a new page based on a page layout every default webpart (as defined with AllUsersWebPart) is instantiated 5 times. Really don't know where this behaviour is coming from, but at least it's not as serious as not being able to edit/publish my pages :)