Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Hi,
I am facing an issue when I use the Followbar in fields content type. and use the field type followbar into views pages. It returns the ajax error, even sometimes it doesn't open the edit popup for fields setting.
Steps to Reproduce.
1. Enable GIGYa module and config it
2. Go to any content type and add fields type gigya followbar.
3. Go to add content and add some content on which content type contains the gigya followbar field.
4. Go to structure and create a views page.
5. Show fields instead of content/teaser etc.
6. Under FIELDS add field type followbar save see.
Output 1 : You won't see the preview of the views page.
Output 2. Try to change URL of the views path and save. it will take you on some ajax error page.
Output 3. Try to edit followbar field, it will not allow to open the popup to edit/remove that field.
I have attached some screenshots to make it more clear and understandable.
Thanks,
Ravindra
| Comment | File | Size | Author |
|---|---|---|---|
| click-on-fields.png | 126.79 KB | RavindraSingh | |
| gigya-followbaron-views-page.png | 341.15 KB | RavindraSingh | |
| gigya-follow-bar-ajax-error-on-page.png | 151.68 KB | RavindraSingh |
Comments
Comment #1
RavindraSingh CreditAttribution: RavindraSingh commentedComment #2
luciodiri CreditAttribution: luciodiri commentedHi,
I was able to reproduce and trace the problem to some extent,
In effect the field is being added to the view.
After you create the follow bar field, you can open the follow bar edit by scrolling to the bottom of the page and selecting it from the content dropdown.
And if you navigate to the URL after you have changed it, you will arrive there safe and sound.
The problem seems to be after submission and creation of the field or the new url.
The page that you are returned to after changing the url is not an AJAX error, but a response object from Views module after the successful change of the URL.
View returns a JSON object that is supposed to be delivered to the html page.
In effect in this case the app header remain json, and so the json object is being displayed.
I could find other mentions of similar behavior in other modules, but they were caused by jQuery Version problems, or wrong directory structure. In this case problem persists with various jQuery versions.
I am changing priority to Normal, since, though it is a problem that needs resolution, the functionality does work.