When I upgraded Sitefinity CMS to version 11.0.6702, I am constantly getting errors when I am trying to edit some custom content types.
Anyway, it works when I upgraded it to version 11.0.6700, but this version has some security issues, which are fixed in 11.0.6702 - at least I hope they are :D .
Error in Chrome console:
Message: Uncaught (in promise): Object: {"code":"","message":"No HTTP resource was found that matches the request URI 'http://localhost/sf/system/newsitems(00000000-0000-0000-0000-000000000000)/Default.itemmeta(state=null)?sf_provider=OpenAccessDataProvider&sf_culture=en&sf_site=4e3e4436-fa80-4108-80bb-55aef99abfd2'.","innererror":{"message":"No routing convention was found to select an action for the OData path with template '~/entityset/key/unresolved'.","type":"","stacktrace":""},"status":404}
Thanks.
Yes, it is a problem with their new upgrade.
You have to override AdminApp folder with new files.
Refer to this article:
https://knowledgebase.progress.com/articles/Article/After-upgrade-to-Sitefinity-11-Hotfix-2-11-0-6702-unable-to-create-items-using-the-new-content-editing-experience
Related
One quick question. As of last week I had completely setup the AEM SDK with the Venia store front with all the components working. When I move the setup the AEM publish SDK, I am encountering one issue.
The /api/graphql is throwing 403 errors which means no frontend commerce operation is happening on the storefront.
I tried adding the /api/graphql to the CSRF filter's exclude list and even removed the POST method from there.
After this I still 403 on GET request of /api/graphql and the following on POST request.
I am I missing some setting?
Note: on the sling servlet resolver config, I have added the /api/graphql but there is no change.
There is a query very similar to this on the groups but there is no response. So thought of raising it here.
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-cif-magento-on-publish...
Please let me know if I am missing something.
Issue solved.
I introduced a var called COMMERCE in the global vars to solve the problem, since the vhost file refers to it.
I could have done it slightly better but I guess i was lazy :)
Please refer to this link for details:
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-cif-magento-on-publish/m-p/442185#M31799
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 have a "SOURCE" module in laravel project. The edit functionality was working fine before I changed the DB. I added a column in DB table "source". After adding it, whenever I try to edit the source data from admin panel, the data gets modified but shows the error: simplexml_load_string(): Entity: line 1: parser error : StartTag: invalid element name
I am using API's in my project where I have used the function simplexml_load_string(). But this was working fine before I added a column to the DB. What could be a possible reason and solution for it?
I figured out the issue. The issue was with my apache server version. To resolve the issue with the CURL extension of PHP, I installed Apache AddOn (Version - 2.4.28) to support PHP (>7.2) extensions. I downloaded the same from here - https://wampserver.aviatechno.net/ and install it at my end. Restart the Wamp Services and choose the updated version of Apache web server. And it was resolved.
In my store have magento community edition - 7.1.
I try to install extension using magento store, but I got an error like this for all type of extensions
community/Dropifi_Dropificontactwidget: Could not resolve host: connect20.magentocommerce.com; Host not found
I placed this key for install magento
http://connect20.magentocommerce.com/community/Dropifi_Dropificontactwidget
http://connect20.magento-commerce.com/community/Dropifi_Dropificontactwidget
Help me to get a result for this issue.
Thanks
I had the same problem ("CONNECT ERROR: Unsupported resource type") while upgrading a 1.6 magento on PHP 5.5.
The unpack function (http://php.net/manual/en/function.unpack.php) has changed.
In downloader/lib/Mage/Archive/Tar.php, the line
const FORMAT_PARSE_HEADER = 'a100name/a8mode/a8uid/a8gid/a12size/a12mtime/a8checksum/a1type/a100symlink/a6magic/a2version/a32uname/a32gname/a8devmajor/a8devminor/a155prefix/a12closer';
must be replaced by:
const FORMAT_PARSE_HEADER = 'Z100name/Z8mode/Z8uid/Z8gid/Z12size/Z12mtime/Z8checksum/Z1type/Z100symlink/Z6magic/Z2version/Z32uname/Z32gname/Z8devmajor/Z8devminor/Z155prefix/Z12closer';
This was not an issue specific to you. Today, the Magento Connect server experienced an outage which prevented any of the community extension keys from working.
The Connect server appears to be online now, so try again and it should work.
Source: https://twitter.com/magento/status/384805097315659776
Helpful Note:
You can download extension packages directly by using the following tool:
http://freegento.com/ddl-magento-extension.php
Just paste in your Magento extension keys and Submit. A downloadable link will appear for you to obtain the package.
i have got this error then try following steps
first you can disable all cache
second after install extension then clear all cache and logout and login
I just implemented a simple login functionality using spring it how ever worked with the eclipse in built browser but gives the following error in chrome and firefox.
HTTP Status 404 - /SpringLogin/welcome.jsp;jsessionid=8332D4F3D4709DCA37C87F30F1EA03D5
The requested resource (/SpringLogin/welcome.jsp;jsessionid=BEE789093FF79CB6B67F8DA368E8B3E4) is not available.
can you please tell me why it is happening?
PS: I have two projects SpringLogin and both of them had same project names and both had similar packages. Then neither of the projects worked properly and gave the above error. How ever after I created another project with a different name and using different package names, it worked like magic. I am guessing here that it may have been the problem. But what is the logical answer that'll explain what happened there?
you don't have being calling the correct URL
it seems that the context /SpringLogin/ does not exists anymore.
Try /welcome.jsp or if you changed the name of application - try /newappname/welcome.jsp