Getting error “Object doesn’t support property or method ‘commitPopup'” when saving a new alert in SP 2010

In my SP 2010 environment, I have a html page, that has an iframe, and the iframe is the page where you create a new alert for a list. In the html page, I dynamically create the iframe and then insert some script nodes in it to run jquery in the alert page.

The problem is, when I click the save button, I get the error message

Line: 1 Error: Object doesn't support property or method 'commitPopup' 

coming from this line (which is the iframe source page)

<script type='text/javascript'>window.frameElement.commitPopup();< 

Does anyone know how to fix this?


Problem with SPO Document Library default view not saving column positions

This seems like it should be a pretty easy task –

I have created a new document library in SPO and added a few columns to it. When I move the columns around, or hide various columns, and the leave the site and return, the column order that I had previously set is not maintained, and the hidden columns are visible again.

This is a new site and I have complete rights to it.

Is there something I’m just overlooking here?

Advanced Custom Fields conflicting with custom plugin when saving custom field

I’m writing a plugin for the practice and running into an issue where another plugin, Advanced Custom Fields is conflicting with my code. I have created a custom post type with it’s own custom field. My save method works and the custom field data is saved if I disable ACF, however I am getting a validation error that I think comes from the acf plugin when trying to save/publish with the plugin active. See pic for the error message.

So I guess my question is, do I need to check if that plugin is active and use it’s functions to handle this and if not do it the normal way, or am I doing something else wrong? Does every plugin that saves custom field data have to check if this plugin is active and handle it accordingly? That just doesn’t seem right to me but this is my first time writing a plugin.

error message

Here is my save method:

public function save_metabox_details() {         global $  post;         if(current_user_can('editor') || current_user_can('administrator') && isset($  _POST['ipmyskills_nonce'])) {             $  nonce = $  _POST['ipmyskills_nonce'];             if( $  nonce && !check_admin_referer( basename(__FILE__), 'ipmyskills_nonce' )) {                 die('Validation error');             }             if (isset($  _POST['ipmyskills_input'])) {                 $  sanitized_value = esc_html( sanitize_text_field( $  _POST['ipmyskills_input'] ) );                 update_post_meta($  post->ID, 'ipmyskills_input', $  sanitized_value);             }         }      } 

Saving preferences & data whne doing clean install of Ubuntu 18.04

I am currently running Firefox & Thunderbird/Lightning in Ubuntu 16.04 LTS.

I wish to do a clean install of Ubuntu 18.04 LTS with a clean install of Firefox & Thunderbird/Lightning preserving ALL my preferences & data from 16.04.

I do a complete backup (via luckyBackup) of the “Home” folder every time I log on.

Which folder/files should I check for to ensure that I can reload my preferences & data?

Thank you

Does the ranger’s companion get to make death saving throws?

I play the role of a cleric in a game that also has a ranger.

This ranger happens to have a wolf as a companion. It happened a couple of times that the wolf fell to 0 hp and was declared dead by the DM.

Even though I know that this creature is a beast and it should die once it reaches 0 hp, I can seem to not be bothered by it since I focus on keeping us alive.

I am aware of the Monster And Death section of the book which states that:

Most DMs have a monster die the instant it drops to 0 hit points, rather than having it fall unconscious and make death saving throws.

Mighty villains and special nonplayer characters are common exceptions; the DM might have them fall unconscious and follow the same rule as player characters.

This here is more in the sense of possibility vs a clear rule stating the fact.

I saw nothing about this in the ranger’s companion section.

Is there a rule or clarification that I would have missed somewhere? I would like if there was a clear rule or clarification on this somewhere that I would have missed.

How do Sanity saving throws work when resisting an effect conferred by an attack or spell that deals psychic damage?

Sanity Saving Throws. You might call for a Sanity saving throw when a character runs the risk of succumbing to madness, such as in the following situations:

Resisting an effect conferred by an attack or spell that deals psychic damage.

A failed Sanity save save might result in short-term, long term, or indefinite madness… (DMG 265-266)

I am playing with Sanity rules and a player is hit with Synaptic Static

  • do they make the initial saving throw with Sanity or just when trying to end muddled thoughts?
  • do I replace muddled thoughts with madness?
  • if the person tries and fails to resist muddled thoughts each turn for the full minute can they end up with 10 forms of madness?
  • can a person have two separate instances of the same form of madness?

SharePoint 2013 Javascript REST API related: Saving Conflict. code=-2130575305, Microsoft.SharePoint.SPException

I have a function which updates list items. I use fiddler 2 for tracking the traffic. When I stress test the function I get code=-2130575305, Microsoft.SharePoint.SPException error, and the error message text is

Save Conflict. Your changes conflict with those made concurrently by another user. If you want your changes to be applied, click Back in your Web browser, refresh the page, and resubmit your changes.

I am using the cross-domain library and my query is

var url = appUrl + "/_api/SP.AppContextSite(@target)/Web/Lists/getByTitle('" + listName + "')/Items(" + itemId + ")/validateupdatelistitem?&@target='" + hostUrl + "'";

and the executor code is

executor.executeAsync({ url: url, method: "POST", body: mappingFunction(dataObject), headers: { "accept": "application/json; odata=verbose", "content-type": "application/json;odata=verbose" },

Is there a way to force SP to delay the attempt to update the item so that it doesn’t throw a concurrency error? Or, what is the right approach to this problem?

Edit: I mentioned some additional information in my comment below. If anyone has any ideas they are going to be highly appreciated. Concurrency conflicts are probably managed easier on the server side, but I am looking to find out if anything can be done from the client side.