I am working on a project in Nuxt which uses Nuxt-Validate. According to the page it uses Vee Validate, I tried using input type='date' with format of dd/MM/yyyy but it wasn't working and I found this on google.
According to the github issue, it should be resolved in version 3 which is VeeValidate but Nuxt-Validate is on version 1.
Does it mean that Nuxt-Validate hasn't got the updated version where they fixed the issue? Is there any way I can use format other the default i.e yyyy/MM/dd
Related
I have used quickblox chat sdk in my old xamarin.forms project. I know that quickblox is not supporting xamarin now, but old sdk was working fine till now, but from last week I am getting this error.
Code:
var baseSesionResult = await Provider.QbProvider.GetBaseSession();
When I am calling QbProvider.GetBaseSession() it throws below error:
CONTENT: {"errors":{"base":["nonce is required"]}}
I have tried different methods available in sdk but none is working. Any one know how to fix this error?
This is Nikolay from QuickBlox support.
Please add "" symbols around nonce and timestamp values and check if the issue is resolved.
The same information is mentioned in our documentation: https://docs.quickblox.com/reference/authentication#create-session
We released a patch for authentication that improves validation according to our documentation.
Hence, the issue is caused by incorrect implementation in the application that is why the server has started showing errors for submitted requests.
I'm facing this issue while trying to call my bot via directline:
As you can see on the image below, my webapi bot project is using the version 5.2.4.0, but according to the log error, the Microsoft.Bot.Conector is trying to use an old version of it ?
Does anybody have a clue on how can I solve it ?
Adding a binding redirection as #Eric suggested worked fine.
I am using the following function to get the version of Datatable I am using :
alert($.fn.DataTable.versionCheck());
But I am getting error as :
$.fn.DataTable.versionCheck is not a function
What is wrong in my code?
The code you are using is designed to check the current version number against the provided version number, for example:
$.fn.dataTable.versionCheck('1.9.2')
will check if the version number you are using matches 1.9.2. You are not providing a parameter to the function.
I believe the $.fn.dataTable.versionCheck() function was added in version 1.10, so if you are running an older version that may explain why you are getting your error message.
You can use the following code to get the version number:
$(document).ready(function(){
$('#myTable').DataTable();
var versionNo = $.fn.dataTable.version;
alert(versionNo);
});
Please see demo here. Hope it helps.
I know this is old, but you can just go to your browser console and run:
$.fn.DataTable.version
I am new to parse and I am trying to figure out how to handle the version number.
I have been deploying some cloud code a bunch of times. So when I last deployed it gave me this message:
Uploading source files
Finished uploading files
New release is named v18 (using Parse JavaScript SDK v1.2.19)
So I thought I could go and hit:
https://api.parse.com/18/functions/someFunctionIWrote
So there I tried to use version 18 because of what I saw after deploying. That does not work and it returns a 404.
So, then I tried to hit:
https://api.parse.com/1/functions/someFunctionIWrote
this works and return the JSON I wanted.
So, what am I missing here?
I thought that every time I deploy the version would match. Do I need to specifically go in and change the current version somehow?
Can somebody help understand how to think about this correctly?
Thank you
If you ran a "parse deploy" it put v18 up there for you the URL stays the same.
The version in cloud can be verified in the terminal by typing: "parse releases"
I have been upgrading a joomla (2.5- to - 3.1) site locally but the upgrade is broken. The sql upgrade did not pass. I have been trying to use the database fix option but even like that did not get it to work in my case.
Database schema version (2.5.11) does not match CMS version (3.1.1).
Table '#__content' does not have column 'title_alias' with type 'VARCHAR(255)'. (From file 1.7.3-2011-10-15.sql.)
I have been trying to execute manually the other query but fails.
How could I fix my broken tables?
Where could I get a valid sql upgrade script?
Try clicking the "Fix" button on the Extension Manager > Database view. If this still does not resolve your issue, you'll need to manually apply all of the fixes. You can grab the SQL updates from GitHub (the same relative file path applies as well) and manually run each file's queries using a tool such as phpMyAdmin. Note you'll need to change the table prefix (#__) to match that of your own site.
had the same problem when doing upgrade 2.5.11 => 3.1.1, fixed it by first using phpmyadmin to add a title_alias field with VARCHAR(50) to #__contents table.
after which joomla added another complaint that title_alias should not exist in 3.0.
After applying 'Fix' I guess the old update scripts for 1.7 first changed title_alias to VARCHAR(255), then the update for 3.0 removed it again, updated the schema version in the db
and joomla stopped complaining...
Hope this helps you.