I'm using Drupal Bootstrap 8x 3.0 beta2 with a sub theme. Whenever I attempt to add new content with the "save and keep published" button, instead of saving the data, it's reverting to the preview page and won't save.

1. I've removed all template and CSS file overrides leaving only the bare bones/starterkit files - problem still exists.
2. I've created a different new sub theme with a new starterkit file replacing all "THEMENAME" with "test" - problem still exists
3. Reinstalled Bartik as default theme - saving content works.
4. Set Bootstrap as the default without a sub theme - saving content works.

As soon as I return to my sub theme, the problem comes back. I've tried my best to self resolve the problem, but I can't figure out why this is happening. Am I missing something? Last update was 12/19/2015 - I'm guessing if it was a bug, someone would have reported it by now?

CSS Snapshot

CommentFileSizeAuthor
#4 2016-02-11_21:20:11-test|bootstrap8.x-3.x-GoogleChrome.png61.2 KBgeneralredneck
image.jpeg263.25 KBcptlonestar
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

matthewjroybal@gmail.com created an issue. See original summary.

raincloud’s picture

raincloud CreditAttribution: raincloud commented

I have the same issue on my brand new and empty D8 site with Bootstrap theme. I didn't even yet create a subtheme or change any settings, just downloaded and enabled the Bootstrap theme.

When creating a Basic Page after pressing Save and Publish I am stuck in a kind of preview page, where only "Back to content editing" link is available and no other action, so I cannot save. Additionally, a javascript error appears in inspector: http://dev.mysite/quickedit/metadata 404 (Not Found). I didn't touch any quickedit module.

On the other hand, when trying to create an Article, after pressing Save and Publish I am back to the edit form and the article is not created. The content of Body field in wysiwyg editor is changed to string "Array" regardless what I typed there before. No javascript error this time.

Of course, after checking the "Use the administration theme when editing or creating content" option in Appearance or changing theme to Bartik, creating content is OK.

cptlonestar’s picture

cptlonestar CreditAttribution: cptlonestar commented

I did a brand new Drupal installation again, added bootstrap and my subtheme. It was working fine for basic pages. When I got a more involved content type, I added field groups and now I'm getting the errors below. It seems to have to do with themes and twig templates, so I'm inclined to think this isn't a problem with field groups. But, I honestly do not know. This is beyond my capabilities. Is anyone able to help?

edit: stack trace moved to http://pastebin.com/bbiqcSvX

generalredneck’s picture

generalredneck
him/his
Primary language English
Location Texas, USA 🇺🇸
CreditAttribution: generalredneck commented
Version: 8.x-3.0-beta2 » 8.x-3.x-dev
FileSize
2016-02-11_21:20:11-test|bootstrap8.x-3.x-GoogleChrome.png61.2 KB

Did a quick test on Simplytest.me and had these same problems. Here are the steps I did

Installed site using Minimal Profile
Installed and set as default Bootstrap 8.x-3.x-dev (note doing so makes it also the admin theme in minimal because the "use admin theme" setting is set to none)
Enabled the Taxonomy Module and Options Module
Created a new taxonomy vocabulary Tags and added 1 term test
Created a new content type "test" and added an entity reference field to "tags"
Created a new piece of content and filled out the required fields. (title in this case)
Clicked Save and publish (Note Save and unpublish does the same thing).

I was sent directly to preview... moreover, there was no way to continue and publish the item
screenshot

A side note...setting "Preview before submitting" to disabled in the content type settings makes it so the "Publish" button doesn't function at all.

markhalliwell’s picture

markhalliwell
Primary language English
CreditAttribution: markhalliwell at Tag1 Consulting commented
Component: Starterkit (CDN) » Code
Category: Support request » Bug report
Priority: Major » Normal

Patches are welcome.

Also, @matthewjroybal, your comment doesn't seem to have anything to do with this issue. Please don't hi-jack issues.

generalredneck’s picture

generalredneck
him/his
Primary language English
Location Texas, USA 🇺🇸
CreditAttribution: generalredneck commented
Assigned: Unassigned » generalredneck

@markcarver
might be worth noting that matthewjroybalgmail.com was the original bug reporter. Don't think he was trying to hijack his own issue... think he was trying to help with additional symptoms... irrelevant or not.

@matthewjroybal@gmail.com
See if you can provide some detailed steps to reproduce. The new issue and go ahead and create a new issue with that and the info you mentioned in #3.

I'll look into a fix for this preview thing since I have steps to reproduce.

markhalliwell’s picture

markhalliwell
Primary language English
CreditAttribution: markhalliwell at Tag1 Consulting commented

Using a single issue as a "catch-all" is still hi-jacking... regardless if it was the OP.

cptlonestar’s picture

cptlonestar CreditAttribution: cptlonestar commented

Sorry I wasn't trying to hijack an issue. I honestly thought it was all related because I got the additional error after clicking "save and publish". I'll create a new issue if it's still there after using the patch. Thank you for the help.

Mile23’s picture

Mile23
Primary language English
Location Seattle, WA
CreditAttribution: Mile23 as a volunteer commented
Related issues: +#2657124: Unable to publish nodes while using Bootstrap theme to create/edit

This issue is possibly a duplicate: #2657124: Unable to publish nodes while using Bootstrap theme to create/edit

markhalliwell’s picture

markhalliwell
Primary language English
CreditAttribution: markhalliwell at Tag1 Consulting commented
Status: Active » Closed (duplicate)