cakephp 3 bin/cake Bake sets user model/controller owner to root - cakephp-3.0

I have just tried the new quick start tutorial in the CakePHP docs.
I have noticed that all user files have the owner permissions set to root and therefor are locked when I try to edit in phpStorm.
Even the directory Template/Users is set to root.
All other files are set to my logged in username.
Is this the expected result? I do not see anything about this in the docs. Should I change the owner of the files?

When you install CakePHP with composer, it sets the directory/file permissions appropriately so that the web server can access the files it needs.
Bake runs as a shell, so when you bake, it creates models, controllers, and views (templates), and whatever else you baked using the permissions of the user you were logged in as when you ran bake.
If you run bake again logged in as a standard user (not root or sudo), PhpStorm should be able to access the files as writable.

Related

Can't access SSRS folders on a local server following installation

edit
I also have the same problem as an admin on a domain
I just installed SSRS locally on a machine for and I cannot access the reports I deployed. Everything was installed as admin
when going to the web portal I get this massage
Could not load folder contents
You are not allowed to view this folder. Contact your administrator to obtain the necessary permissions.
and when trying to access the web service via the config manager I get this one:
The permissions granted to user <username> are insufficient for performing this operation. (rsAccessDenied)
Additionally in the web portal I got no "manage" folder and only "my subscriptions" under the settings button .
Everything is running locally and as admin, the OS is windows 11 and the SSRS is version 15.0.1102.1002 and running in native mode.
I've looked all over the place and found out something about certificates, but almost everything in google is about access problems via remote server.
adding the URL to the trusted sites didn't help
it certainly look like you don't have permission. Are you administrator? When you were installing did you set up some users to be administrators?
Find which account is administrator and then add yourself from the SSRS site. Is there another account you can run or Run as administrator?
Another way to install again.
If you decide to install again pay attention on the page with the users.

Using dbms_scheduler.create_credential on a exedata

I want to setup a file_watcher for file created in a location in the OS. We are currently using Jobs that access the files through utl_file.fopen to access the files using a directory entry.
I ask my DBA to setup a credential so I can establish the file watch using dbsm_scheduler. He told me that because we are using a exadata appliance for our database we could not create the credential. I dont get it! If we are accessing the file through a directory why is a issue access through a credential?
Any Ideas?

WordPress cannot write file to disk

So my website was hacked a few days ago and after that I did a fresh install of wordpress.
I proceeded to install my theme, everything went smooth. But when I wanted to upload files in the media folder via wp, it said cannot write file to disk.
I tried a few more times and it worked, I uploaded like 5 images and it stopped working again same error.
I also cannot install plugins via wp I have to do it manually, and I had to install my theme manually too... I am going crazy called my web hosting they said it's wordpress fault.
You will need to review permissions of wp-content/* folders and files and subfolders. Folders should be 755 to support writing into them by WordPress. You can set this in most FTP client software by use of CHMOD feature.
You may also need to review owning user and group of wp-content/* folders and subfolders and files. Owning user and group should match the Linux user and group that your server software operates under (i.e. user www-data or apache)
wp-content/uploads for media uploads, thumbnail image generation
wp-content/themes for theme installation, automatic updates, and use of Editor
wp-content/plugins for plugins installation, automatic updates, and use of Editor
Do you have SSH access into your server? That's easiest way to verify and change ownership user/group and permissions.

Wordpress Reinstallation - You don't have permission to access /sitename/ on this server

We've been working hard on a sandbox server. We installed WordPress to it from scratch. I created the database, and imported the previous database into it. The user and password both have been created.
Right now, our error is "403 Forbidden: You don't have permission to access / on this server". I can't access any of the files by typing in the server IP address,though we see and control everything as root via Putty, or manage it through FileZilla. Root is the owner of all WP files/folders.
I found this source: WPBeginner-403-Error-Fix and am currently changing the permissions on the files; the folders are done and the permissions are set to 755. File permissions are being set to 644. Out of all the resources we had referred to, it never mentioned WP requiring specific permissions. I got right onto that today. While this is running, I still get the message after the folder permissions were changed, and as the file permissions are being processed:
You don't have permission to access /wp-admin/login.php on this server.
We also had a bootstrap file located in the same place as the WP installation / contents (this was a test). The bootstrap is very much accessible: the CSS/JS folders with the supporting content can be seen if you type the ipaddress/directory for the bootstrap version... you can see the files and structure. If you type in ipaddress/boot.html, it runs it flawlessly. If we try referring to anything with WP, it does not like it and throws the 403 error.
There is no .htaccess, I read online it would generate via permalinks in the panel. But we can't even see the panel. It's currently .htaccessOLD (from when we imported our old WP contents to the dev server, from the production site), so there should be no interference.
None of us has installed WP directly, the guy who did it previously no longer is part of the company, so we are becoming lost in this process.
Edit: Plugins were disabled via renaming convention, however, WP actually regenerated this folder.
Edit (2): With the permissions set, and the plugin/theme deactivated, it still does not run due to 403.
Weird... my answer didn't post yesterday as I had thought.
So- we solved it. The permissions were set accordingly for all directories/files, the issue was the server configuration. Just triple check the server configuration file (usually httpd.conf on current servers) to ensure it points to the directory containing the WP contents.
If this is still a problem to some people, and you swear that the httpd.conf file is correct, it does not hurt to double check your directories. The directories should be permission 755. Files should be 644, excluding the wp-config.php (that ought to be set for permissions 455).
Thank you for helping us troubleshoot! We really appreciated it! :)

phpMyAdmin on IIS7.5 permission not granted

I am trying to get phpMyAdmin working on a server with IIS7.5 installed. We have done the following and cannot get access to phpMyAdmin working:
MySql installed
Windows Server 2008 running IIS7.5
Followed this tutorial: enter link description here
Created a new site and added phpMyAdmin directory beneath it as an application (I can see the subdirectories of the phpMyAdmin root on this application)
Navigating to the subdomain set up for the application indicates we do not have sufficient permissions. I gave users and administrator read/write access for the site and the application:
HTTP Error 401.3 - Unauthorized
You do not have permission to view this directory or page because of the access control list (ACL) configuration or encryption settings for this resource on the Web server.
I feel like we are very close, but I am unsure what other permissions need to be set to gain access.
I'm not used to IIS 7.5, but I believe typically you would need to give the IIS user read permission on the phpMyAdmin folder, files, and subdirectory. You mention giving permission to users and administrators, but I don't think the IIS user would fall in to either of those categories.