cakephp undefined class constant AttachmentBehavior::CROP - cakephp

Fatal error: Undefined class constant 'AttachmentBehavior::CROP' in /var/www/manage/lib/Cake/Utility/ClassRegistry.php on line 168.
I have been getting this error after I was done following the steps on this page to setup access control lists. http://book.cakephp.org/2.0/en/tutorials-and-examples/simple-acl-controlled-application/simple-acl-controlled-application.html .
The error shows up when I deny access to an action which requires authentication. When I grant access to an action, I can use it just fine. The error also shows up on one particular action whether I deny access to it or not.
My version of cakephp is 2.3.4 and I am using the plugin from http://www.alaxos.net/blaxos/pages/view/plugin_acl_2.0/ to manage my permissions.

AttachmentBehavior::CROP belongs to a plugin called Uploader which wasn't loaded. problem solved

Related

Trigger execution warnings with Logic App Standard on Azure Function Runtime

I've got a Logic App (Standard) running on an Azure Function runtime, and I've noticed I'm getting spammed with warnings for my O365 When a new email arrives in a shared mailbox (V2) trigger.
Trigger is meant to execute on cluster type 'Classic'. However, it is executing on cluster 'NotSpecified'
Just Created a Logic App (Standard) and created an O365 trigger on a shared mailbox v2 trigger.
Allowed the trigger to fire
Log Stream/AppInsights will show the warning about trigger execution: Trigger is meant to execute on cluster type 'Classic'. However, it is executing on cluster 'NotSpecified'
There can be several reasons for the error that is mentioned above. One way to solve this problem is by reconfiguring the O365 Logic App Connection and try again.
Usually it happens when there is a version mismatch of the library reference or older version of the component referenced in logic app. If still the error persist, error handling need to be implemented properly in logic apps to get detailed error. App Insight will give proper error log and provide us the error logs if issue still persist.
Please check this Handle errors and exceptions in Azure Logic Apps documentation from Microsoft for more information.

delete_model() error when cleaning up AWS sagemaker

I followed the tutorial on https://aws.amazon.com/getting-started/hands-on/build-train-deploy-machine-learning-model-sagemaker/
I got an error when trying to clean up with the following code.
xgb_predictor.delete_endpoint()
xgb_predictor.delete_model()
ClientError: An error occurred (ValidationException) when calling the DescribeEndpointConfig operation: Could not find the endpoint configuration.
Does it mean I need to delete the model first instead?
I checked on the console and deleted the model manually.
No, you don't need to delete the model prior to deleting the endpoint. From the error logs looks like its not able to find the endpoint configuration. Can you verify if you are setting delete_endpoint_config to True
xgb_predictor.delete_endpoint(delete_endpoint_config=True)
Additionally, you can verify if the endpoint_config is still avaiable on the AWS console.

ds.addToCatalog() for Angular-Wakanda

Is there anything like ds.addToCatalog() in Angular-Wakanda? Problem is that once the DataStore is loaded (ex. init("Employee")), it is not possible to add new DataClasses if needed.
I'm trying to loady only the DataClasses needed for each Angular-Controller.
The reason different access rights for different Angular-Controllers, meaning that if a user with limited acces rights logs in the .init() method would throw the following error because the user has no access to all DataClasses:
GET http://127.0.0.1:8081/rest/$catalog/$all/ 401 (Unauthorized)
Loading only the DataClasses with access rights works fine:
http://127.0.0.1:8081/rest/$catalog/Page,%20Employee,%20News/
There is actually a bug on Angular-Wakanda connector that is causing this issue.
When $wakanda.init() is called the first time (whatever the parameter given to the function), the returned dataStore is cached connector-side, and directly returned to further calls to $wakanda.init().
Wakanda team is aware of this issue and it will be fixed soon.
There is no possible workaround at this time, unless calling $wakanda.init() without parameter to retrieve the whole catalog. But it won't properly work according to the access rights you have set on your dataClasses.

How to resolve Joomla Fatal Error : JApplicationCms::getUserState()

I got this error after Global Check In:
Fatal error: JApplicationCms::getUserState() [japplicationcms.getuserstate]: The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "Joomla\Registry\Registry" of the object you are trying to operate on was loaded before unserialize() gets called or provide a __autoload() function to load the class definition in /home/societ/societ.us/libraries/cms/application/cms.php on line 504
I don't know where the problem is.
I'm currently using Joomla 3.2.3
It's fixed when I clear the cookies, but happens again when I'm navigating to Global Check In page.
The problem was caused due to active session (not closed properly) in the Joomla! sessions table.
Follow below steps to resolve these errors:
Login to cPanel.
Access the DB using PhPmyAdmin.
Delete all the user sessions from the 'vnto1_session' table.
Now website is accessible without any errors.

Error while executing query for custom object Work Order

I am executing the query for my custom object created in SFDC. but i am getting the following error:
{'[{"message":"\nSELECT FS_Account_Name__c from FS_Work_Order__c\ERROR at Row:1:Column:34\nsObject type 'FS_Work_Order__c' is not supported. If you are attempting to use a custom object, be sure to append the '__c' after the entity name. Please reference your WSDL or the describe call for the appropriate names.","errorCode":"INVALID_TYPE"}]'} Thoough have written the correct table name as given while i created the Custom object. PLease help.
First thing to try: does it work properly when run as the system administrator profile? If so then it's certainly a permissions issue. Things to checl
The object is deployed (Setup > Create > Objects > Edit > Deployment Status)
The profile has permission to query the object.
If not, does that same query work from inside the developer console? If so I can't think of what it might be, except connecting to production instead of a sandbox or vice versa.

Resources