in-mem-update.xqy not found in MarkLogic 8.0-6.4 - admin

Has anyone faced the below error when running the application without admin user in MarkLogic 8.0-6.4
Module /opt/MarkLogic/Modules/MarkLogic/appservices/utils/in-mem-update.xqy not found
The import is specified as follows in one of the application modules
import module namespace mem = "http://xqdev.com/in-mem-update" at "/MarkLogic/appservices/utils/in-mem-update.xqy";
We are facing with one of our users who is running the application without admin privilege. As soon as we assign admin privilege to that user, everything starts to work magically again for that same user.
Do we need to assign any specific privilege for /MarkLogic to resolve to the global MarkLogic modules (/opt/MarkLogic/Modules/) directory?
Or is there any specific setting we need to do for non-admin users?

You should not need any special role or permission to access modules under /Modules/MarkLogic/.
Check if there are other imports on modules living in some modules database. It sounds like you have a custom library with inappropriate document permissions, and the error message is simply pointing to the wrong file. I've seen this before with the lazy evaluation of XQuery inside MarkLogic.
HTH!

We found the resolution to our problem. The error itself was misleading though. This issue occurred due to someone manually deploying library module with wrong set of permissions. Once we fixed the permissions, we were golden.

Related

Opencart Forbidden access after swapping to previous database

Good day,
I had created my online store on a VPS, I opted to move the store to a web hosting package. After installing opecart using softalicioucs the default installation worked fine. I then edited the config files in both admin and public_html to change the database to the original backup of my VPS.
Once I do this, "You don't have permission to access this resource. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request".
If I go back to the installed default database its all good again. I have set the necessary permissions etc for the user to access the backup database.
Anyone knows what is going on? is there some table storing access information?
After disabling MODSECURE I realised that the new installation created tables with prefixes not as my original interfaces, hence the solution was to change the prefix in the config file.

Unable to explore tables as admin in apache superset

I've just installed apache superset following instructions at https://superset.incubator.apache.org/installation.html. I then login to the web interface as admin. I also loaded sample data with 'superset load_examples'.
If i go to 'Sources > Tables' and click on any of the tables ('wb_health_population', for example) i get an error: 'This endpoint requires the datasource wb_health_population, database or all_datasource_access permission'.
I check permissions set for the admin role and existing permissions: 'all_datasource_access' is not enabled for the admin role, and does not exist in the list of existing permissions.
As i told, i just followed standard instalation instructions from superset's doc website. Any help on this? Thank you.
EDIT: Superset version is 0.20.6, python's 3.6.3.
Try running superset init - this should initialize permissions.
See https://superset.incubator.apache.org/installation.html#superset-installation-and-initialization
(code-wise, init calls security.sync_role_definitions() which itself calls create_custom_permissions() which creates the said permissions)
I would also try all_database_access permission.

Can't get access to configuration.php Joomla 2.5

Got a site to make some changes. Unfortunately I can't get an access to www/root/configuration.php . Suppose the file was blocked by another user who had admin rights. Am I right?
I'm not clear exactly what you mean by 'can't get access' to the configuration file. Maybe it's permission related or maybe the site was customised and the configuration file is in a non-standard location.
Either way there are a couple of options you could try.
I presume you have access to the backend of the site and so you could make most changes from there via Site > Global Configuration.
You can also view almost all the details of the config file from Site > Sytem Information > Configuration File
If neither of these suggestions solved your problem, maybe you could instal a file management component like http://extensions.joomla.org/extension/extplorer and acces the config file that way.
Good luck!

Using django-admin in deployed project

I am working with django, and I would like to use django-admin to manage certain things of my site, including the mantainance of the database.
Can I use it once the project is deployed or should I consider other options? I have searched for options but I didnt find anything. Leaving the admin site like www.mysite.com/admin I dont think is an option because of security issues.
Thanks
The django admin is exactly what you should be using to administrate (hence the name) your site after deployment. What are the security issues behind www.mysite.com/admin? You need a user account with staff privileges to access the admin area.

How do you access the Doctrine service in an imported parameters file in Symfony2?

I asked a recent question about how to load your own parameters in Symfony2, which was answered here How do you load config settings from the database in Symfony2?, but I now need to know how to actually access the database in the import file.
I have tried using:
$container->get('doctrine.orm.entity_manager');
Unfortunately, I then get a "The service definition doctrine.orm.entity_manager does not exist." error.
Can anyone help?
Your code should work.
$this->container->get('doctrine.orm.entity_manager');
But only if Doctrine is enabled.
Have you the Doctrine Bundle in your kernel ? Have you uncommented the doctrine settings in config.yml ?
After asking and looking around for a while the only solution I found to accessing doctrine while Symfony is still configuring its services is using this bundle. Take a look at the readme as it describes a solution to the scenario we are both experiencing.