search

backdrop-contrib / title

Replaces entity legacy fields with regular fields.
GNU General Public License v2.0
0 stars 2 forks source link

Stuck at "Replacing field values for %" page (but conversion works in the background). #5

Open klonos opened 8 years ago

klonos commented 8 years ago

So, I edited the page content type and clicked on the "replace" link and on the next confirmation page I enabled the "Replace title with a field instance" checkbox and clicked "Save settings". I then got stuck to a "Replacing field values for title" page with a progress bar that seemed to be doing nothing:

backdrop-contrib-title-stuck_on_replacing_values_page

...I waited a while, and then decided to open the Page content type edit page on another tab of my browser (while leaving the page with the progress bar running) just to check if anything happened in the background. And I got a confirmation message:

backdrop-contrib-title-title_replaced_with_a_field_instance_confirmation_message

Checking the "Manage fields" tab shows that it worked indeed.

klonos commented 8 years ago

...forgot to mention that the path of the page was batch&op=start&id=9 if that helps at all.

serundeputy commented 8 years ago

thanks @klonos!

fixed up some more language issues to allow the batch to complete and redirect rather than complete and hang.

klonos commented 8 years ago

Hmm, still seems to hang for me. This time, I tried replacing the Post content type title. When stuck at the progress bar page, instead of opening /admin/structure/types/manage/post/fields in another tab, I tried opening it in the same browser tab as the stuck batch progress bar. I momentarily got an AJAX error and got redirected to the manage field page, but the redirect happened so fast that I only got a glimpse of it before I could get a chance to copy the exact error.

klonos commented 8 years ago

...although there are some other errors related to the Title module logged in /admin/reports/dblog (I'll file a separate issue for those), there is no sign of the AJAX error 😕

klonos commented 8 years ago

...now that I think about it, before testing if this issue was fixed, I tried testing the fix for #3 and I had enabled the option to automatically replace the title with a field for nodes in /admin/config/content/title. Does that work on a node base or should there not be an option to replace the title in the manage field page (because it is set to be replaced automatically). Hmm, maybe I don't understand what this option is supposed to do exactly. Anyways, thought that I should mention this in case it helps to reproduce the issue.

serundeputy commented 8 years ago

ahh;there is a config change associated with this. so either uninstall and reinstall or we need an update hook; our both

On Oct 3, 2016 2:39 PM, "Gregory Netsas" notifications@github.com wrote:

...now that I think about it, before testing if this issue was fixed, I tried testing the fix for #3 https://github.com/backdrop-contrib/title/issues/3 and I had enabled the option to automatically replace the title with a field for nodes in /admin/config/content/title. Does that work on a node base or should there not be an option to replace the title in the manage field page (because it is set to be replaced automatically). Hmm, maybe I don't understand what this option is supposed to do exactly. Anyways, thought that I should mention this in case it helps to reproduce the issue.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/backdrop-contrib/title/issues/5#issuecomment-251188859, or mute the thread https://github.com/notifications/unsubscribe-auth/AGc0l8BoaTJmc5eP0LJB6oD9ibuUkzKRks5qwUvXgaJpZM4KKrSn .

klonos commented 8 years ago

There is no official release yet, so I'm pretty sure that there are not many sites using this module. I say don't waste your time. I'll uninstall and reinstall.

...by the way, what happens when this module is uninstalled? Are the default titles reinstated for nodes, taxonomy and comments? Guess we'll find out soon. Thank goodness this is on a local test that I can blow up anytime 😝