Open ericraskin opened 9 years ago
Tried a "clean-all" instead of "clean". Unfortunately, that did not help either.
Hi, It could be the assets pipeline plugin.
Is there a particular version I need? I have asset-pipeline:1.9.9
On 04/06/2015 02:49 PM, Tudor Malene wrote:
Hi, It could be the assets pipeline plugin.
— Reply to this email directly or view it on GitHub https://github.com/tudor-malene/Easygrid/issues/146#issuecomment-90195016.
Eric H. Raskin 914-765-0500 x120 Professional Advertising Systems Inc. 914-765-0503 fax 200 Business Park Dr Suite 304 eraskin@paslists.com Armonk, NY 10504 http://www.paslists.com
Umm, try a newer one. For ex 2.1.5
Will do. Thanks.
On 04/06/2015 02:53 PM, Tudor Malene wrote:
Umm, try a newer one. For ex 2.1.5
— Reply to this email directly or view it on GitHub https://github.com/tudor-malene/Easygrid/issues/146#issuecomment-90196522.
Eric H. Raskin 914-765-0500 x120 Professional Advertising Systems Inc. 914-765-0503 fax 200 Business Park Dr Suite 304 eraskin@paslists.com Armonk, NY 10504 http://www.paslists.com
Unfortunately, that did not fix it.
On 04/06/2015 02:53 PM, Tudor Malene wrote:
Umm, try a newer one. For ex 2.1.5
— Reply to this email directly or view it on GitHub https://github.com/tudor-malene/Easygrid/issues/146#issuecomment-90196522.
Eric H. Raskin 914-765-0500 x120 Professional Advertising Systems Inc. 914-765-0503 fax 200 Business Park Dr Suite 304 eraskin@paslists.com Armonk, NY 10504 http://www.paslists.com
I had to add a dependency to get a production war file to build after upgrading to asset-pipeline:2.1.5:
dependencies {
...
compile 'com.google.guava:guava:18.0' // required for asset pipeline
...
}
Then another refresh-dependencies, clean-all, compile. Unfortunately, that did not fix it either. :-(
On 04/06/2015 02:53 PM, Tudor Malene wrote:
Umm, try a newer one. For ex 2.1.5
— Reply to this email directly or view it on GitHub https://github.com/tudor-malene/Easygrid/issues/146#issuecomment-90196522.
Eric H. Raskin 914-765-0500 x120 Professional Advertising Systems Inc. 914-765-0503 fax 200 Business Park Dr Suite 304 eraskin@paslists.com Armonk, NY 10504 http://www.paslists.com
You could try to compare the html of the page rendered with 1.6.6 and with 1.7.1 Maybe we spot something.
Good idea. Trouble is I can't find any difference. Any ideas on how to do this comparison, other than manually on the Firefox Inspector screen? The pages are buried pretty deep in my application, behind Spring Security logins. It's hard to just do a wget or a curl. :-/
On 04/06/2015 03:33 PM, Tudor Malene wrote:
You could try to compare the html of the page rendered with 1.6.6 and with 1.7.1 Maybe we spot something.
— Reply to this email directly or view it on GitHub https://github.com/tudor-malene/Easygrid/issues/146#issuecomment-90207834.
Eric H. Raskin 914-765-0500 x120 Professional Advertising Systems Inc. 914-765-0503 fax 200 Business Park Dr Suite 304 eraskin@paslists.com Armonk, NY 10504 http://www.paslists.com
Question: How does Easygrid know when to render a child grid? That seems to be the problem here. It seems to be trying to jump to rendering the child grid before a master row is chosen.
On 04/06/2015 03:33 PM, Tudor Malene wrote:
You could try to compare the html of the page rendered with 1.6.6 and with 1.7.1 Maybe we spot something.
— Reply to this email directly or view it on GitHub https://github.com/tudor-malene/Easygrid/issues/146#issuecomment-90207834.
Eric H. Raskin 914-765-0500 x120 Professional Advertising Systems Inc. 914-765-0503 fax 200 Business Park Dr Suite 304 eraskin@paslists.com Armonk, NY 10504 http://www.paslists.com
Hmmm... There is something that seems different upon closer inspection. On 1.7.1 Easygrid, I am seeing "::before" and "::after" in the Web Console. I don't see those things on 1.6.6. What are they?
Version 1.7.1:
Version 1.6.6:
Note the ::before and ::after tags in the 1.7.1 version. Where are they coming from?
So I dumbed down one of my pages to a single grid and it still displays incorrectly. I get a Warning box with "Please, select row" at the bottom of the page and the page is grayed out:
You can just make out the cross-hatching in the screen shot. That should not be there.
Any idea where I can look now? The GSP contains:
<html>
<head>
<meta charset="utf-8">
<meta name="layout" content="main"
<title>Professional Advertising Systems Inc.</title>
</head>
<div class="row">
<div class="col-md-6">
<p>Click on a Mailer to view their merge jobs</p>
<grid:grid name="brokerMailers" >
<grid:set altRows="true"/>
<grid:set width="500" height="auto" caption="Mailers" />
<grid:set col="id" hidden="f:true" />
<grid:set col="company" width="250" label="Mailer"/>
</grid:grid>
</div>
</div>
</html>
I have tried commenting out portions of this, but I still get the same issue.
Could the problem have something to do with jquery or jquery-ui versions? My bootstrap-enabled website loads the latest versions from code.jquery.com. Is there any way to stop your plugin from loading them as well -- if you think that could be the problem?
Well, I've found the problem. For some reason, the jqgrid CSS files are not being pulled in by the asset-pipeline. When I load them directly from a CDN, everything works perfectly again.
I don't know enough about how asset-pipeline works with plugins to help you, but this is what you have in easygrid.jqgrid.css:
/*
*= require /jquery-ui/jquery-ui.css
*= require /jquery-ui/jquery-ui.theme.css
*= require /jqGrid/ui.jqgrid.css
*/
I'll bet it's the capital "G" in jqGrid. The directory entry in your plugin is assets/stylesheets/jqgrid (not jqGrid).
Hi:
I've upgraded my project from 1.6.6 to 1.7.1 (refresh-dependencies, clean, easygrid-setup, compile). When I now execute my project, any page with a grid comes up "crosshatched out" in Firefox and Chrome. I also see "Warning: Please select row" in dialog boxes at the end of the render. Of course, it all worked fine before the upgrade.
I do see the grids rendering properly and loading with data.
Note that my pages have master/child grids. It is behaving like the child grids are trying to load before any rows have been selected in the master grids.
What might have changed that could cause this?
Example code: