I remove the inherit of standard the from my module and replaced for:
<inherits name='com.google.gwt.user.theme.clean.Clean'/>
But my project still includes the standar theme, and after the clean:
<link rel="stylesheet" href="http://127.0.0.1:8888/formulariorequerimientos3/gwt/clean/clean.css">
<link rel="stylesheet" href="http://127.0.0.1:8888/formulariorequerimientos3/gwt/standard/standard.css">
So the styles are mixed and I see the horrible dialogbox of standard theme, please help!
Probably caching issue. Shut down you dev IDE and server serving the app .It's should really be in hosted mode.Clear browsers cache. Shut down your machine and restart. You will not have to do this all the time but sometimes caches get stuck. Also make sure there are not error in IDE and and check sever log as well (meaning logs from hosted mode server) to see any errors being thrown.
Check your War\Webapp if you see clean/clean.css then delete clean folder altogather. Also suggest Project->clean if you are using eclipse.
The problem is that I wa including a module (one of UI utils) that inherits standard theme, so I replaced for clean
Related
I have updated my module from moodle 3.2 to moodle 3.5 and receive these errors in the debug web console:
moodle-core-event: Global event published: FORM_ERROR
yui_combo.php?rollup/3.17.2/yui-moodlesimple.js:5828 moodle-core-event:
Global event published: BLOCK_CONTENT_UPDATED
These errors show when opening a pop up with atto editor so notes can be saved. Unfortunately, I can't save the notes and it seems the above errors are causing the issue.
I have tracked down a similar error on the moodle forum site:
https://moodle.org/mod/forum/discuss.php?d=367647
However, no solution has been marked. Sadly no apache errors are showing so I can't narrow down the problem.
Can someone shed some light on these errors?
Just checking the obvious, but did you purge the caches? Javascript is cached
Administration > Site administration > Development > Purge all caches
or
php admin/cli/purge_caches.php
I always turn the cache off in config.php in a development environment $CFG->cachejs = false; but never on production, which has caught me out before.
Also, you might need to run grunt to minify the javascript files, then add the minified files to the git repository
https://docs.moodle.org/dev/Grunt
If your javascript is in a folder called amd
grunt amd
If your javascript is in a folder called yui/src/something
grunt shifter
Or just
grunt js
I am trying to start debugging session using built-in WebStorm server after I created a new JavaScript debug configuration. I am using this project:
https://github.com/pauldessert/SeedTip.git
I am experiencing this weird problem that all of my locally referenced .css and .js files:
<link rel="stylesheet" href="css/reset.css">
<link rel="stylesheet" href="css/style.css">
<script src="js/map.js"></script>
<script src="js/search.js"></script>
...could not be found/loaded by the browser. I show this in bellow image when I pressed F12 to see Chrome Dev tools (this action seems to disconnect WebStorm IDE support extension) and you can see failed requests.
You can see in the console tool window in WebStorm that there were get request for .css and .js local files. When I press any of these links it opens ok in my Chrome browser.
E.g. this file does exist:
http://localhost:63342/SeedTip/css/style.css
When I use an external node server e.g. grunt-serve and create JS debug configuration with URL: http://localhost:9000/index.html pointing to:
F:\Projects\Angular\v2\SeedTip and run this debug it works.
Note: I have the same problem with enabling Angular 2 apps to load with systemjs.
I tried setting but it doesn't help.
I was a known bug, that was fixed in the latest build.
I'm rewriting my question to be more detailed and more clear.
i have a project like this:
com.mycompany.modulue1
------------------------------------>client
------------------------------------>server
------------------------------------>shared
------------------------------------>module1.gwt.xml
com.mycompany.modulue1
------------------------------------>client (JSNI - create a method to access methods in module2)
------------------------------------>server
------------------------------------>shared
------------------------------------>module2.gwt.xml (using add-linker name="xsiframe")
in module1.html i added the following script:
"script type="text/javascript" language="javascript" src="module2/Module2.nocache.js"
"script type="text/javascript" language="javascript" src="module1/Module1.nocache.js"
now i get "module2" need to be recompiled every time (even if the env. is clean and recently built
the JS method that is defined in module 2 is not defined when the server is up.
i'm using external server in dev mode (for EJB use)
What I'm doing wrong?
Thank you
Ahmad Igbaria
Not sure I fully understand your problem but judging by the title:
If you have a page that loads 2 distinct GWT applications, you can run only one of them in DevMode by subtituting gwt.codesvr in your URL with gwt.codesvr.moduleName, where moduleName is the name of the module to run in DevMode. That way, the other module won't switch to DevMode and will thus run in production mode.
This however only works with the xsiframe linker (for the one module you want to run in Dev Mode at least)
After so much time and headaches, I have found the solution it's very simple, you need to add the linker to both modules not only the one you want to use as a pre-compiled!
on a particular page on our site http://www.sakshum.org/ui/page/JoinUs.jsp which is build using gwt and deployed on GAE the module does not load.
This works fine in development env in eclipse and have no errors when looking via firebug in the console.
Please advise what may be wrong here and how to fix it?
look at the AE logs. firebug will only show you client side stuff. It's probably a classpath issue -- such as you have something locally but aren't uploading that jar ...etc.
Edit:
please post your JoinUs.jsp
I am calling my gwt module via a jsp page on AE no problem. Maybe the path in your script tag pointing to the *.nocache.jsp file is off somehow. Usually when things resolve locally but not on AE, for me, the problem was appengine-web.xml and setting include and exclude paths. I had to be careful there because things worked differently locally and deployed - especially using wildcard.
Also, look for uri errors under the dashboard (ae administration page). static resources that are not found will show there and not in the ae log since they are static.
Thanks all for the help. So, the issue was completely different. Actually the div tag was not rendering at all due to the coding error of a if statement in the jsp. On fixing that it started working
Currently I am developing a GWT project by using GWT 2.4.0 in eclipse 3.7. I deploy the app inside Tomcat 7. It run perfectly for the past 2 months.
However, now I am running into a problem which I unable to trace the problem. Here is the source code for "welcomeGWT.html".
<!doctype html>
<!--
The DOCTYPE declaration above will set the browser's rendering engine into
"Standards Mode". Replacing this declaration with a "Quirks Mode" doctype may
lead to some differences in layout.
-->
<html>
<head>
<meta name='gwt:module' content='com.haircare101.cesapp.Main=com.haircare101.cesapp.Main'>
<title>101 HairCare: Customer Excellence System</title>
</head>
<body>
<script type="text/javascript" src="com.haircare101.cesapp.Main/com.haircare101.cesapp.Main.nocache.js"></script>
</body>
</html>
As the tomcat started, I type the corresponding URL into browser and it shows me this page with no error (no error shows inside Tomcat log files). But it unable to direct me to the specified GWT Main Entry Point (I saw this source file when I can "View Source" of browser).
** I have no compilation error, no deployment error or no runtime error.
Can anybody tells me the reason why it stuck in this page? Many thanks and appreciate!
Cheers,
Ryan C.
Besides using google chrome, enable firebug to debug your javascript and find out what's wrong. Apparently you have an array acess problem.
Most probably, it is in your GWT entry point and not in javascript (don't forget that all the client package code is transformed into javascript)