This is getting super exciting!
I'd tried a previous combo of Popups API and subedit and gave up on it.
Now trying with most recent versions.
Loving the stackable popups BUT. . .
. . . everything seems to be working OK 'cept after clicking to edit my fieldgroup, then editing and clicking on "SAVE" the popup hangs.
I get the "loading" animation and the grey screen forever, until I click on the page to deactivate the popup.
I really hope you can get this sorted out 'cos I LOVE where you're going with this.
Thanks!
Comments
Comment #1
austintnacious commentedOK, I've been trying to get this to work for a while now, considering possible conflicts with other modules. . .
I turned off checkout.module and got the "Save" button to work to an extent.
Now when I click "Save" i get the final status popup which says "Bad response form submission".
When that popup is dismissed (either automatically via the Popups admin setting or by clicking OK) I get a white screen with the output quoted below. . . (I have no idea what to make of that).
When I go back to the node page and refresh my edit has been saved but something isn't working right, as you can see.
Any ideas, I hope I'm being more of a help "testing" this than a hinderance. . .
Also I got a popup at one point indicating a conflict /error with ajax.module ("unknown error has occurred") I have not tried disabling it yet. . .
Comment #2
austintnacious commentedOK, while I can definitely confirm the conflict with checkout.module I am getting closer to working things out and getting subedit to work on my site.
. . . the value of reading the README. . .
I read in the read me . . .
I had a look in my page.tpl.php file (I'm using a very CSS modified "Basic 6.x-1.2" theme, I've made no changes to the theme's php).
Basic uses "echo" rather than "print"
I'm not a programmer but I know that echo and print do roughly the same thing although they may have deeper significance for programmers.
I changed echo to print for $content in my theme and uploaded.
Subedit appears to be mostly working now, except I still get the "Bad response form submission" error with the final dialogue.
My edits are saved tho'!
So maybe I should submit a feature request to ask that you make subedit handle both print and echo. . .
I also notice that I don't get the drupal default node updated message.
I like getting those messages as when I do I assume that everything is working well together.
When I don't get the drupal system message I feel / think/ know something isn't working quite right. . .
Comment #3
starbow commentedWow, you've got at lot going on in your page. Just at guess, but ajax and shadowbox both seem like modules likely to conflict with popups.
I think echo and print are the same thing, although Drupal devs never use echo. I didn't know any themers did.
Your first step is to just get Popups API working on your setup. A good test is to enable the popup test module, go to popups/test, and try some of the links there. Especially the "Change Settings and ajax update entire content area" which tests a basic form modifying the original page. Toggle the "Auto Close" setting and see if the value in the parentheses changes....although, come to think of it, it is possible that this test is broken in Alpha4. Try the "Change Settings and reload entire page." first. If that doesn't toggle the values, then the test is broken.
Comment #4
austintnacious commentedHi, thanks for the response!
I'll try the test as you describe.
It got late last night and I gave up so now I can't remember exactly where I got to but I have the following additional observation(s).
Popups subedit has trouble with Drupal's caching system. Stops working in various ways. Right now though with all chaching off all I'm getting is the whole node edit form in the popup, rather than just the fieldgroup. . .
Comment #5
austintnacious commentedTried the tests, the popups seem to be working OK 'cept they don't seem to be behaving 100%.
Like if I understand your response above then when I try some of the tests, toggling the auto close last dialogue checkbox does not change the value in parentheses at the original link on the popus/test page.
So there also seems to be a bit of a conflict with the Node Edit Protect module.
Like I'm getting slightly better usability having disabled that module.
Yes, I do have a lot going on on the site but isn't that the beauty of Drupal?
I guess I need to ask straight up if you think that popups API and subedit etc are likely to get to a stage where they can co-exist well with other modules.
I love where you're going with it and would really like to use it but I can't sacrifice caching and other bits of functionality / protection offered by other modules. . .
Happy to test along the way if you're heading towards broad compatibility. . .
Comment #6
bfr commentedPrint returns a value and echo does not, so echo is marginally faster, and they have slightly different syntax. No other differences.
I usually use echo, but in some situations you can make use of prints return value.. like some functions or more complex expressions:
or
Comment #7
chien_fu commentedI'm having an issue similar to this, except it was working fine a minute ago. I made no changes except to change the values of a couple CCK field on some nodes. One time it worked fine and the next time a tried it, on another node, I get the popup and when I try to save it now just hangs forever on the loading graphic.
Okay.. so I went back to a node that originally worked and it worked correctly again, so it depends on the particular node that I'm editing. What could be the cause of this?
Comment #8
glarsch commentedI also was experiencing this issue. For me, it turned out that it was 2 fields causing the issue. Both fields were file upload fields. Once I removed those fields, the pop-up saved correctly.