I have installed a version of Odoo 12 via the Debian/Ubuntu package on a server and one version of Odoo 12 running local directly from the source code.
On the test server i can not see fields which are decorated with "group='base.group_no_one', while i can see these options on my local version.
Within both systems all my users are part of the default group "Extras / Technical Features" / "base.group_no_one".
I don't know why this is happening. Since all runs basically on the same code base i expect the views to be rendert the same way on both systems.
Still no data is displayed within the views.
I also get no error message.
To see the fields with the group base.group_no_one you need to activate developer mode in "Settings > Activate the developer mode" (in the settigns board on the right side).
Also you can add ?debug=1 to your Odoo URL, for example: http://localhost:8069/web?debug
Related
I have a MAUI application that I put into source control; then pulled down and attempt to develop on a different machine; on the second machine, in Visual Studio 2022 I no longer had the option to run "Windows Machine" it was replace with the name of the project and it wouldn't run it attempts to start but breaks in App.g.i.cs with the message
System.DllNotFoundException: 'Unable to load DLL 'Microsoft.ui.xaml.dll' or one of its dependencies: The specified module could not be found. (0x8007007E)'
How do I setup a MAUI application such that I can run it on different development PCs?
Steps to Replicate / Steps to Confirm Issue
To confirm the issue / attempt to see what the difference is I did the following
Machine 1: Create MAUI App from Template (no changes); confirm "Windows Machine" option for debugging; and it runs as expected
Machine 2: Create MAUI App from Template (no changes); confirm "Windows Machine" option for debugging; and it runs as expected
Copy Code from Machine 1 to Machine 2: Windows Machine option not available; application won't start up with above exception
Copy Code from Machine 2 to Machine 1: Windows Machine option not available; application won't start up with above exception
Use Git to compare the two applications: looks like only difference is OpenSans-Regular.ttf and OpenSans-Semibold.ttf and the ApplicationIdGuid ... note if change those values (copy files, change guid) it still won't permit Machine 1 code to have "Windows Machine" Option on Machine 2
Assumption: I'm assuming there is some difference between the two machines that is causing this; but I'm not sure how to determine that difference and resolve; both are running VS2022 17.3.6 64-bit; Xamarin 17.3.0.296; .NET Core 6
It seems the symptom that show the issue is that the MauiApp showing that "Windows Machine" as an optio to run up the application; if the App was created on the Machine you get that; but if you pass that code to another machine you see the csproj name and get this exception
Desired Outcome: My goal here is to have a single code base, committed in Git, that I can develop on two different machines with a MAUI App; no worries if there are settings or similar to support; or if one machine needs updates; just how to determine and get to that state is the issue / question.
Any help on resolution; or what that would happen (note: all non-Maui apps work across these two machines; console apps, windows services, web api, web app etc... commit on one; run on the other; it is only Maui apps having this difficulty)
Resolution: launchSettings.json not put into source control; copy launchSettings.json and everything works as expected
It looks like the issue here was less about the machine this was running on; and more that launchSettings.json were not on the target machine when transferring code
I copied the launchSettings.json from the template created to the target machine and things worked as expected from there.
I worked all day to get Xampp running and install TYPO3 on it. Now I'm logged in the backend, but many admin modules are not displayed, such as Templates, Access etc. - There must be something I've done wrong, but I've got no idea. these are the modules shown Missing: View, Info, Functions, Template, Access, Backend Users, Log, DB Check, Configuration, Reports.
Most backend modules are shipped as extensions, which can be installed, uninstalled, activated and deactivated.
If you installed TYPO3 by using the traditional installation method (extracting the TYPO3 source package), go to ADMIN TOOLS → Extensions and make sure, the missing modules are activated. For example, "Log" is provided by the system extension belog and "Templates" by tstemplate. You can activate/deactivate extensions by clicking on the icon left-hand-side of their title.
If you installed TYPO3 by using PHP Composer (see documentation), make sure all packages are included in your composer.json file. For example typo3/cms-belog, typo3/cms-tstemplate, etc. You can add/remove packages with the following composer commands on the command line (for example typo3/cms-belog):
composer require typo3/cms-belog
composer remove typo3/cms-belog
In the unlikely event that this does not solve your issue, review file typo3conf/PackageStates.php. This file contains a list of all extensions (system extensions, as well as community extensions), currently available in your TYPO3 system.
It could also be that your admin user, who may have been migrated from an older version, is not a newly introduced system maintainer.
https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/9.0/Feature-82266-BackendUsersSystemMaintainers.html
If that is the case, you can easily create an new "system maintainer user" from the install environment. Maintenance > Create Administrative User
I had the same problem. The required extension were also present in PackageStates.php but still the backend menu options like Admins Tools, Extensions, Maintenance were not visible.
The reason was that that admin user was not listed as a System Maintainer
To make a backend user a System Maintainer do the following
Login with admin password to /typo3/install.php
Setting > Manage System Maintainers
select and save backend users you want as System Maintainers
Now go to backend at /typo3/ and you should see the "Admins Tools" menu options
You can use https://get.typo3.org/misc/composer/helper to figure out the missing extensions. If you simply want to install all extensions, klick on TYPO3/FULL and copy and paste the code to your console.
composer require "typo3/cms-about:^9.5" "typo3/cms-adminpanel:^9.5" "typo3/cms-backend:^9.5" "typo3/cms-belog:^9.5" "typo3/cms-beuser:^9.5" "typo3/cms-core:^9.5" "typo3/cms-extbase:^9.5" "typo3/cms-extensionmanager:^9.5" "typo3/cms-feedit:^9.5" "typo3/cms-felogin:^9.5" "typo3/cms-filelist:^9.5" "typo3/cms-filemetadata:^9.5" "typo3/cms-fluid:^9.5" "typo3/cms-fluid-styled-content:^9.5" "typo3/cms-form:^9.5" "typo3/cms-frontend:^9.5" "typo3/cms-impexp:^9.5" "typo3/cms-indexed-search:^9.5" "typo3/cms-info:^9.5" "typo3/cms-install:^9.5" "typo3/cms-linkvalidator:^9.5" "typo3/cms-lowlevel:^9.5" "typo3/cms-opendocs:^9.5" "typo3/cms-recordlist:^9.5" "typo3/cms-recycler:^9.5" "typo3/cms-redirects:^9.5" "typo3/cms-reports:^9.5" "typo3/cms-rsaauth:^9.5" "typo3/cms-rte-ckeditor:^9.5" "typo3/cms-scheduler:^9.5" "typo3/cms-seo:^9.5" "typo3/cms-setup:^9.5" "typo3/cms-sys-action:^9.5" "typo3/cms-sys-note:^9.5" "typo3/cms-t3editor:^9.5" "typo3/cms-taskcenter:^9.5" "typo3/cms-tstemplate:^9.5" "typo3/cms-viewpage:^9.5" "typo3/cms-workspaces:^9.5"
We are in process of upgrading Sitecore 6.6 to 7.2. Part of upgrade is to migrate all the media items from 6.6 to 7.2.
I tried creating a package but the package size is too large and times out on package installation.
I found link below using Powershell Console where it shows copy-item command:
http://blog.najmanowicz.com/2011/11/18/sample-scripts-for-sitecore-powershell-console
I attached the 6.6 to 7.2 version where I can access the 6.6 DB. However copy-item doesn't seem to support different databases.
Could someone please help how I can use SiteCore Powershell or similar to migrate media items from 6.6 to 7.2?
I had a similar issue with a (very large) media library with a similar migration. Packages seems to bomb out around the 2GB mark, instead serialize the items:
Delete everything from /Data/Serialization
Open the media library. Makes sure you have the Developer tab
showing (right click somewhere on the toolbar and enable it
otherwise)
Select your root media item then Serialize Tree
Wait...
Copy the serialized files from /Data/Serialization to your new
server
From the toolbar select Update or Revert Tree depending on your requirements
Profit.
You can find more info in the Sitecore Serialization Guide and this post by Brian Pedersen
You should be able to do this in Powershell too (from my understanding). You need to:
Add the database to your connectionString.config
Add that database to your web.config to <sitecore><databases><database>. You can copy the existing master node and rename the id attribute to match your conneciton name
Your legacy database should now be connected to Sitecore interface, you can check it is present in the database selector list from the right of the desktop
The powershell command now needs a "from" and "to" location. Assume your database is called "legacy_master", the following should work:
copy-item "master:\media library\*" "legacy_master:\media library\"
I've found Hedgehog TDS (and sometimes Razl) quite useful for doing this.
Create a new TDS project (don't version control it), and download all the items you need to your local machine. You can for example connect the "Debug" build to your source 6.6 instance, and a "Release" build to your target 7.2 instance. Then you can just synchronize the items to your target machine. It's sometimes good to synchronize one or a few branches at a time if you have long latency connections.
The good thing about this is that you're in total control of your content and can see what fields are updated etc. During an update process, it's sometimes useful to compare other parts of the db as well, just to ensure you don't miss any changes you've made to the platform.
Since I mentioned Razl as well: I've found Razl quite good if you have a whole branch that you know should be transferred from one db to another (such as the case you describe). TDS is a bit slower, but more universal - and you may have a TDS license already so it may not be worth an additional Razl license.
I've just added item transfer from one DB to another so you can Copy-item between databases starting with Sitecore PowerShell Extensions 3.0. Thanks for the great idea!
Just to add another option you can perform tasks like this using Revolver.
WARNING: Try this in a test environment first
if we assume that:
the context item is the media library item
the current database is master
the target database is called master72
then something like this should work:
cp -r -n master72/sitecore/
My problem is that my content does not show at all on particular device/browser and only once bundled. The wep app display correctly in debug (running it from meteor) whatever the device or browser are.
EDIT : I can see the navbar and the footer but not the yield on affected devices/browsers
Affected devices/browser known to date are Chrome on Nexus 4 (not on Note3) and Dolphin on Note 3.
Dev environment is Windows and prod is Linux.
I've also tried to run the app through meteor directly on server and the problem is not here but is back even when I bundle the app from the server.
Any idea about what can cause that and/or how to troubleshoot that?
EDIT 2
I can finally confirm that it's a client side bug.
Here is the error from chrome console on the device
Exception from Deps recompute function: ReferenceError: Lists is not defined
at Object.Template.layout.helpers.lists (http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:31:25567)
at http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:10:5624
at Object.e.call (http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:27:20793)
at HTML.DIV.HTML.UL.UI.Each.UI.block.e [as __sequence] (http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:27:28178)
at http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:10:4102
at http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:9:3419
at a (http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:2:4791)
at n.extend._compute (http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:2:5846)
at new e.Computation (http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:2:5183)
at Object.n.extend.autorun (http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:2:7042)
But the Lists collection is defined, published and subscribed. And the weirdest part is that everything works well when debugging through Meteor
In my specific case, Collections definitions were located in a /collections folder at the root of the app. That caused the app to load them after the /client folder but only once deployed and on some devices/browsers only!
To fix that, I've just move the /collections folder into /lib, bundled it again, push it to the server and everything now works flawlessly whatever the device/browser is.
I have a small team of web developers who work together on up to 50 external sites. I am trying to find a better solution to using Dreamweaver's check-in check-out for managing source. We have just started using Visual Studio 2012 here and there and I am curious if TFS is the way to go for us. No one here has ever used versioning or any type of source control before, so I am looking for something similar to what they are used to.
If it matters at all, our sites are all hosted on a Windows 2008 R2 server, and largely written in C#.
I think TFS is a good option to consider. As several people have commented, it will be a jump from what you are your team are used to in Dreamweaver, but I personally feel if you are serious about managing your intellectual property, you will invest in some sort of version control system. With that said, there will be a learning curve regardless whether you are your team select TFS, SVN, Git, etc.
Assuming you do go with TFS, you do get the added benefit of everything else that comes with TFS - it's not just about version control. This includes work item tracking, automated builds/deployments, reports, a simple SharePoint site, etc.
With TFS you get the benefit of all of these features, combined into a single product. You can accomplish a similar setup using open source products as well, but would require you to piece the products together.
I'd use the integrated Subversion client in Dreamweaver, which does the basic stuff very nicely and doesn't require the tedious navigation process that will lead to your team bypassing the system. Only problem, DW does not support the latest versions of SVN so you need to pick up an SVN server that is compatible. Try this:
Setting Up Version Control for Dreamweaver CS6 on Windows
Any previous attempts to get version control working may well have created some .svn folders and files on your PC. You MUST remove ALL of these and UNINSTALL ALL OTHER VARIETIES of Subversion software from your PC before you start.
Go to the VisualSVN Server website and download an archived standard version of their software, version 2.1.16 . Don’t be tempted to grab a later version, because this will install SVN 1.7 or 1.8 and neither will work with Dreamweaver.
http://www.visualsvn.com/server/changes/
Trying to get DW working direct to a local folder using the file:// protocol probably won’t work and is also known to put data at risk. You need the server. I chose to install the VisualSVN server with the default settings, other than opting to use Windows logins and go with HTTP, not HTTPS. I decided to have the repositories live on an internal SSD drive, but any local drive will do. When creating a folder for your repositories to live in, use a name that is pretty general e.g. ourcorepositories . I used lower case for everything.
Right click on ‘Repositories’ to create a new one. Give it a name without any spaces or special characters e.g. mynewprojectrepo and check to ‘Create default structure’ . Before you OK, note the Repository URL and copy it into Notepad or a similar plain text editor so you can refer to it later during 6 below. It will be something like
http://OFFICEDESKTOP/svn/mynewprojectrepo
Notice that the capitalised part of the URL is the name of your computer. Click OK and you now have a repository for your project.
5. Boot DW and go to your project. If you don’t have a project yet, create one and stick some dummy files and folders in it. Go to Site menu>>Manage sites… and 2-click your project. Select Version Control.
6. Set Access to be ‘Subversion’ (no other choices exist), Protocol to be HTTP and for the Server Address enter the name of your computer in lower case e.g.
officedesktop
For the Repository Path enter (e.g., using current example from 4. Above)
/svn/mynewprojectrepo
The Server Port should be 80 . For the Username enter your Windows user name, in lower case. Enter your Windows password for the Password. This is the name and password combo that you use to log in to your PC . Click the Test button and you should get a success message. If not, the best advice is to delete any .svn files and repositories you have created and start again. Be sure not to add any slashes or omit any; the above works. Before you click Save, click the link to the Adobe Subversion resources and bookmark it in your browser. There is a lot of useful background information there. Click Save, click Done.
7. Go to your DW project and open up Local View. All of your site’s files and folders will have a green + sign beside the icon. Right-click on the site folder and click ‘Version control>>Commit” . It is a very good idea to leave comments whenever you change anything, so leave a Commit Message along the lines of “The initial commit for My New Project” and click to Commit. If you have a lot of files to go to the repository, they’ll take some time to upload. As they upload, the green + signs disappear to show that you local version is in synch with the repo.
8. Okay, that’s it, you have Version Control in Dreamweaver CS6. It may also work in CS5 and 5.5. Check out those Adobe resources for some good insights on workflow. I can’t help with any other ways to implement version control, but I can maybe save you time by saying that DW doesn’t integrate with Git and that the basic, but integrated, Subversion client in Dreamweaver is way better than having no version control. For coverage against physical disaster, I’d also add in a scheduled daily backup of your entire repositories folder to some cloud storage.
Apologies for any errors. I’d recheck all of the steps, but A) I think they’ll get you up and running and B) it’s easier to do the install and set up the first time than the second time (all those .svn files and folders to get rid of).