I have done a default installation of Magento 2.2.5 CE and when I click on an order in the Magento Admin I get the following error:
"Order View. Information changes have been made to this section that have not been saved. This tab contains invalid data. Please resolve this before saving".
The problem is that I haven't done any messing with the back end code and its a default install. Where am I going wrong? There doesn't seem to be any other error messages. (I haven't turned on developer mode). When I go into the Module Manger there are no modules listed so I don't think its that. I don't have any extension installed.
I'm baffled. Any help greatly appreciated.
Mike
Disabling module Temando_Shipping fixed that
Related
Hi everyone I am experiencing a problem with my Backpack license, I bought the license for a single project, and I have inserted the license into my .Env file as described in the documentation:
BACKPACK_LICENSE=XXXX-YYY-ZZZZ-XXXX-YYY-ZZZZ.
And set APP_ENV=production.
The system seems to recognise the licence correctly (no yellow warning is shown when logging in), however when I try to edit my users, the yellow warning appears with the words: "User editing is disabled in the demo version".
What's wrong?
I should point out that I have not activated the cache, but as a test I have also run the command as suggested: php artisan config:clear, but I still get this warning.
Can anyone help me? Thank you.
It sounds like you've created your project starting from the Backpack demo. That's just an example Laravel + Backpack installation, to show off its features, it should not be used for real-life projects. Notice the demo docs page says:
Don't use this demo to start your real projects. Please use the recommended installation procedure. You don't want all the bogus entities we've created. You don't want all the packages we've used. And you definitely don't want the default admin user. Start from scratch.
I recommend you create a new Laravel project, then install Backpack on top of it, then copy-paste your custom code in that new project. That will not only fix the inability to edit things, but many other problems like the ones listed in the quote above.
We have several action console projects. But recently I could not access to one of our action console projects.
Normally I will access from list in here:
https://www.screencast.com/t/CWlbqhRFc
But now it always show error when I click to one of our projects in there.
https://www.screencast.com/t/b6DmCIcmDsec
I contact with google and ask them for helping. They said that it is caching problems and ask me clear cache on browser. I did it but error still happen. Many other members of this projects also got that error (We shared account of project with some members).
Does someone know the reason of this bug and how could I fix it?
Please check the Roles you have for the project. You need to give Viewer Role to all the members of the project who are getting this error.
Please have a look into this Stackoverflow post as well.
There are a high chance there are a problem in google server. Because after we add a new device model. We could access our project again.
We upgraded a TYPO3 installation from 8.7.x to 9.5.19.
Afterwards, the User-Icon dopdown in the top toolbar is missing. (see screenshots)
We found out that the toolbar is generated in this class:
/typo3/sysext/backend/Classes/Backend/ToolbarItems/UserToolbarItem.php
We see that there have been lots of changes here since v7.6 but don't know where to go from there.
Is there a configuration file, where the items in the top bar are noted?
Additional information: we are working with the typo3-themes extension and have worked with our own theme before the update. During the update we switched to the bootstrap4 + bootstrap4-child theme - would this be a starting place for further investigations?
Before upgrade:
After upgrade:
UPDATE: It seems like this was at least not the root of the problems. After reactivating typo3_console the user-icon was still visible. So it looks like we have further investigating to do.
Update (2 Days later):
We can't reproduce the error. My best guess for now is, that deactivating the extension "repaired" a corrupt configuration file which had caused the disappearing of the user settings icon. After a lot of researching i have not found anybody with a similar problem so this might be an edge case. I wish i could offer more insight to this.
Thanks to Peter Kraume's basic suggestions i found the answer: after i deactivated the extension typo3_console it immediately worked!
Just for the record, here are the other steps we tried:
BE (via top bar)
Flush frontend caches
Flush all caches
BE Admin Tools ("Maintenance")
Flush TYPO3 and PHP Cache
Remove Temporary Assets
Logs
BE System log shows no current errors
Shared Hosting, /var/ contains no logs, /logs/ contains ftp and access logs
Hosting Provider Backend
Cleared OPcache
Created a new Admin-User, logged in, same behaviour
Tried on two different PCs
Primarily tested on Firefox 77.01, checked with Chrome 83.0.4103.116
Extensions:
was not sure, which extensions might manipulate the topbar - deactivated typo3-console, because i remembered seeing some error during the upgrade process. My feeling was more like: i don't need this right now, so i could as well deactivate it. 1 second later, the user drop-down reappeared. Unbelievable! Thanks for reminding me of the basic stuff - like turning off things!
We just had the same problem after upgrade from TYPO3 8 to 9. I have compared the working BE-User with the non-working BE user. They differ in given Language. Working BE-User has lang=''. Non-Working BE-User lang='de'. After switching the working BE-User to lang de, too, the UserToolbar is gone. I have updated the languages in Maintenance-Module and now everything works as expected.
Solution for us was to disabling the "belog" extension.
I had the same problem and I could solve it on all systems with:
Install-Tool > Maintenance > Manage Language Packs > Download the files again.
I've tried posting this on the Umbraco forums to no avail. Hoping to find some help here.
I thought I upgraded successfully from 4.0.4.2 to 4.5.2 (on my way to 4.8...) as I received no errors and everything seemed to go smoothly. However, in the backoffice, when I click on any section other than Content, I get redirected back to Content. I can manually reach each section by typing in the name of it after the # sign like: #media, but as soon as I click on a tree item, it redirects me back to Content. Any ideas would be appreciated.
2 thoughts:
You're cacheing some of the old javascript in your browser. Try clearing your cache. IE can be stubborn in this regard; preferably try in Chrome.
Personally, if your site is working under 4.5.2, I wouldn't sweat the back office issue and just continue with the upgrade to 4.8.1. There will likely be new problems to solve there anyway :) and the backoffice issue may go away.
Updating the icons via the following script fixed this problem. Links must run off the appIcon field. Not sure why this is not executed when the database is updated via the 4.5.2 upgrade.
update umbracoApp
set appIcon = '.tray' + appAlias
where appAlias IN ('content','media','users','settings','developer','member')
I'm coding some PHP files on Eclipse IDE, and I keep getting an error that says "Building Workspace has encountered a problem" -- Workspace is the name of my project area.
When I click on the "details" link I get this
Errors occurred during the build.
Errors running builder 'JavaScript Validator' on project 'Ullman'.
java.lang.NullPointerException
As mentioned, I'm working in PHP so I don't know why it's trying to set up JavaScript Validator. I can't figure out how to stop it from doing these things. Anyone know?
I'm not experienced, so please provide a detailed answer if you can.
I just ran into this problem myself and the previous accepted answer was not helpful. The problem is not the validator, it is the build. To fix go to Project -> Properties -> Builders, then disable ‘JavaScript Validator’. Since you are working with PHP your build is getting confused when you try and validate a PHP file with a JavaScript validator.
The error message doesn't really do anything it just gets annoying really fast.
http://blindcoder.wordpress.com/2011/03/04/javascript-validator-problem-in-eclipse/
Project->Properties->Builders then disable 'Javascript Validator
http://blindcoder.wordpress.com/2011/03/04/javascript-validator-problem-in-eclipse/
UPDATE: Cleanshooter's answer is the better one for PHP-specific projects. I'm leaving this answer since it is useful for people who run across the error on JavaScript files because of crashes in the JavaScript parser.
You can disable part of the JavaScript validator with Eclipse -> Preferences -> JavaScript -> Validator -> Errors/Warnings and unchecking Enable JavaScript semantic validation
I am using the Spring Source Tool Suit IDE and i have fixed this issue by following the below steps :
select the Project and choose the properties option.
Select JavaScript > Include Path option and then choose the Source tab.
Click on Edit button and Click Add button.
Now enter the value for Inclusion Pattern as *.js then click on Ok button and Finish.
I have solved my problem in this way. Please let me know if any one have any other way to solve this problem.
Just go to Project -> Build Automatically and disable this option.. you won't need it anyway with PHP.. because there is nothing to be build.. but this solves the NPE thrown at each save or f5 action
For those of you who are having trouble with 'dynamic web projects', you may find that none of the other answers work.
I tried all the options stated here and found that disabling the 'Faceted Project Validation Builder' solved the problem..
right click project --> Builders --> uncheck the 'Faceted Project Validation Builder'
I ran into the same problem and the above suggestions would not resolved it completely unless until I came across to this post # How do I remove javascript validation from my eclipse project?
But even then after doing all (as given the other post url), had to manually removed the "Problems" tab statements like 'Errors' and 'warning' then only it goes away completely at least in Eclipse Juno.
Hope it helps someone.
This is a problem that has happened to me on some Web Dynamic projects. Every time the project is built, I get this error:
Errors occurred during the build.
Errors running builder ‘JavaScript Validator’ on project ‘some-project’.
java.lang.NullPointerException
At a first sight it seems that a Javascript validator is throwing a NullPointerException, so probably you will try to disable Client-side Javascript validation from Project->Properties->Validation… but I tell you that the problem is not there, you must go to
Project->Properties->Builders
then disable Javascript Validator.
Problem solved.
Project->Properties->Builders then disable 'Javascript Validator,
this fixed my problem:
Errors occurred during the build.
Errors running builder 'JavaScript Validator' on project 'xxx'.
29
This is a problem that has happened to me on some Web Dynamic projects. Every time the project is built, I get this error:
“Errors occurred during the build. Errors running builder ‘JavaScript
Validator’ on project ‘some-project’. java.lang.NullPointerException”
At a first sight it seems that a Javascript validator is throwing a NullPointerException, so probably you will try to disable ‘Client-side Javascript’ validation from Project->Properties->Validation… but I tell you that the problem is not there,
you must go to Project->Properties->Builders then disable ‘Javascript
Validator’.
Problem solved. Indeed is not a real problem, but the message is a bit annoying because it happens in every build
in my case, right clicking on project -> "Project->Properties->Builders then disable 'Validation" worked for me.
I had the same error. It happened after adding the D3 js libraries.
My solution to get rid of it:
-I moved the libraries to a server and the html page gets them from there.
-Removed the libraries from the project as they weren't needed there.
Problem solved for me.
Recommandation:
- remove the latest added libraries from your project and see if the error message disappears.
- get the libraries dynamically (in the html) from a server but do not have them in your project.
It doesn't solve the root of the problem but it does help to get rid of immediate frustrations.
Good luck.
Disabling ‘Javascript Validator’ is not the ideal solution. It is just hiding the problem.
What worked for me is this:
Switch to a new or a different workspace from File >Switch Workspace
and then import your existing project into this new workspace.
Problem solved.