Not writing to database

It may just be an error from when you pasted the code into your message, but you seem to be missing some quotes.

Have you verified that the data you are posting is correct for all users?

Those are actually two single quotes. For some reason it won't write if I just say {value: arLastLoginDate});

HI PerBonomi 

is your $.post surrounded by some sort of <#if condition or you're certain that the post is performed but no data is actually modified on the server?

Nico

Oh, I see. '' + arLastLoginDate will force JavaScript to convert arLastLoginDate to a string.

Have you debugged the JavaScript to see what value it is actually submitting to the API? You can do this in most browsers by opening developer tools (F12) and going to the Net tab. You should see the post made by jQuery, and be able to read the raw data. You'll want to make sure that URL and the data are valid.

---

NicoB wrote:

HI @PerBonomi 

is your $.post surrounded by some sort of <#if condition or you're certain that the post is performed but no data is actually modified on the server?

 

Nico

---

It's surrounded by one IF:

<#if user.registered>

---

nathan wrote:

Oh, I see. '' + arLastLoginDate will force JavaScript to convert arLastLoginDate to a string.

 

Have you debugged the JavaScript to see what value it is actually submitting to the API? You can do this in most browsers by opening developer tools (F12) and going to the Net tab. You should see the post made by jQuery, and be able to read the raw data. You'll want to make sure that URL and the data are valid.

---

Yeah, it looks alright. Funny thing is, I switched to a user where it wasn't writing and it wrote this time.

It seems to be specific to where the user is, maybe what browser they're using, or something..

I would personally suggest to refactor the $.post call and make it a bit more rubust.

$.post returns a promise so you can leverage this pattern to do something in case of success or error so that you can track what happens a bit better:

$.post('/restapi/vc/users/id/${user.id}/profiles/name/field1/set', {value: '' + arLastLoginDate})
  .done(function(){  
    // Everything went well. Maybe you don't have anything to do here
})
  .fail(function(){
    //You could log the error somehow or you might want to retry..
  });

---

NicoB wrote:

I would personally suggest to refactor the $.post call and make it a bit more rubust.

$.post returns a promise so you can leverage this pattern to do something in case of success or error so that you can track what happens a bit better:

 

$.post('/restapi/vc/users/id/${user.id}/profiles/name/field1/set', {value: '' + arLastLoginDate})
  .done(function(){  
    // Everything went well. Maybe you don't have anything to do here
})
  .fail(function(){
    //You could log the error somehow or you might want to retry..
  });

 

---

Interesting! I'm definitely doing that retry once.

I am running two other $.posts more or less at the same time. Is it possible that the write attempts are too close together?

Another thought: could it be mobile users? I only have the code in the desktop wrapper..

And if so, does this kind of code work on mobile?

If the code is in the wrapper so it definitely could be the problem because the wrapper is device specific therefore you need to replicate the same code for the mobile wrapper.

As per the call being too close, it shouldn't be a problem because the community by nature is transactional so it should be able to handle close or even simultanous calls.

Thanks,

Nico