If I create some content in the regular view, then click advanced for more options, the content disappears. Changes made on one tab (standard, advanced, hidden) are not reflected when changing tabs without first saving information. This is further a problem because htmlarea will not work in the standard view, only in advanced. I seem to remember at some point with this module, all options appeared on hidden. So clicking the "hidden" tab would create a view with everything in standard, advanced, and hidden. Going back to this may be the simplest work around for this problem.

Comments

pyromanfo’s picture

pyromanfo commented

Do you have javascript enabled in your browser? Clicking on a tab should submit the form with javascript, that's all that's necessary to keep the info between tabs.

jasonwhat’s picture

jasonwhat commented

Yes, I'm using Firefox and do have java enabled.

pyromanfo’s picture

pyromanfo commented

Are there any specific fields or is nothing being saved?

pyromanfo’s picture

pyromanfo commented

What I mean is, is any of the information staying at all?

jasonwhat’s picture

jasonwhat commented

no, no information is staying at all. If I check the box for "sticky" or enter content in the body, nothing stays between. Also, sometimes when I switch tabs I'm unable to go back to the original view using the back button, just get stuck.

pyromanfo’s picture

pyromanfo commented

You're not supposed to use the back button, you're supposed to click on the tab to go back. Clicking on anything but the node types ("forum","book",ect.) or "advanced" or "hidden" will make you lose all your information.

jasonwhat’s picture

jasonwhat commented

Well, what is a user supposed to do when some options are only available under the hidden tab, and some only under standard or advanced. And if you go to the advanced tab, but want to get back to standard view there is no way to do this.

pyromanfo’s picture

pyromanfo commented

When you switch between hidden or advanced tabs it keeps your info. So if you select "Read Only" on the comments on the hidden tab, then switch to the advanced and make changes, both sets of changes are applied when you submit. To get back to the basic tab, you click on the node type. I may add a "basic" tab down there near "advanced" and "hidden" for clarity though, as that is a little counter intuitive now that I think about it.

jasonwhat’s picture

jasonwhat commented

but what if the field doesn't show up in both advanced and hidden? For example, I have taxonomy select as standard, if I switch to switch to advanced, the body field is still there, but taxonomy select is gone, and the taxonomy I selected before I switched won't be saved.

I have the author/ promotion/comments field only in hidden, if I update this in hidden, then switch back to advanced, the options aren't saved. Should all fields be shown in hidden, including standard and advanced? I thought that is how it used to work, but doesnt now.

pyromanfo’s picture

pyromanfo commented

but what if the field doesn't show up in both advanced and hidden? For example, I have taxonomy select as standard, if I switch to switch to advanced, the body field is still there, but taxonomy select is gone, and the taxonomy I selected before I switched won't be saved.

No, it will be saved as it's saved in a hidden form field by quickpost. Quickpost sees what you don't currently have shown on this tab and outputs the values for that as hidden form fields. It all makes it back to Drupal when you click submit.

jasonwhat’s picture

jasonwhat commented

Aha! Well this is what isn't happening for me then. Especially when doing an edit. I just tested a few and there is no saving and resolving once posted. Not sure why.

jasonwhat’s picture

jasonwhat commented

Maybe this is an issue with htmlarea which is also using some javascript? I don't know, but it certainly isn't working for me which is too bad. Has this been working properly for anybody else?

pyromanfo’s picture

pyromanfo commented

Hmm that's a very likely possibility, thanks. I'll try to find time to take a look at it, but now that I know you're using HTMLArea this may be easier to reproduce.

jasonwhat’s picture

jasonwhat commented

any updates here? My temporary solution will be to move most things to hidden where only I need them anyway. But I still can't figure out how to make sure all node posting uses quickpost. I need to use the new "node relativity module," but don't know how to have it use quick post when I create a new node attached to another node. You mentioned some code I could change but I couldn't figure it out. Plus shouldn't this be standard, that the module makes sure all instances of "add node" use quickpost?

pyromanfo’s picture

pyromanfo commented

ah, I finally figured this out when upgrading to 4.6.0.

You have to edit your theme to output the 'attributes' member of the link items as the attributes of the menu link. For instance I edited 'friendselectric' (PHPTemplate) to do this.

function phptemplate_menu_item_link($item, $link_item) {
  /* Wrapper span */
  return l('<span class="lw1">'. check_plain($item['title']) .'</span>', $link_item['path'], array_merge(array_key_exists('description', $item) ? array('title' => $link_item['description']) : array(),$link_item['attributes']), NULL, NULL, FALSE, TRUE);
}

I merged the existing $link_item['attributes'] with the new attributes created from the description. That way the javascript makes it to the browser and it all works fine.