strapi - Set roles permissions - delete role automatic onSave - strapi

When I set roles permissions it deletes automatically when I hit the save button, only when on the server, when we try it on localhost it works perfectly.
Does somebody know what the problem could be? or have a solution like setting it to default on code or another solution?
before clicking Save
after clicking Save
I tried to set default on code or create another simlar route with a diffrent content.

Related

Magento 1.9 - cannot login to admin after renamed Document Root

I have a subdomain say dev.domain.com that points to document root public_html/dev.
Worked fine, but for good reasons I renamed the folder dev to devm19, also modified the subdomain to point to public_html/devm19.
Problem is I can't login to the admin - The form for UN and PW is there, credentials are correct, but the form key in URL bar keeps refreshing, you just can't get inside to admin.
Any idea?
See the result of the below SQL
select * from core_config_data where path like '%web/cookie/cookie_domain%';
If it gives you "dev.domain.com" in the value field, then either make it blank or give "devm19.domain.com" as value.
Then flush the cache, open the admin panel in private window and you will be able to login.
I was able to solve the issue by modifying app/etc/local.xml.
Added/replaced records for:
<session_save><![CDATA[files]]></session_save>
<session_save_path><![CDATA[/tmp/session]]></session_save_path>

Magento - change store view to default via phpmyadmin

Situation: I have messed up the store view option in Magento admin (very right option in 'Manage Stores'. I tried adding another store view. After saving it, I could neither enter backend nor was the frontend visible anymore (404 error).
I have access to phpmyadmin and was planning to manually change the store view to default again, but did not find the the aproporiate location to do so. Could you guys point me to the right direction please?
(I saw a similar question asked on this board, but with unsatisfying solution: 404 error in front end and admin of magento after changing store view to a new store)
Found this myself though:
core_store
core_store_group
Dont forget to delete the cache and sessions or your website wont load properly:
/var/cache
/var/sessions

Joomla ACL: Only allow access to custom component in the backend?

I'm building a component for the backend. I don't want the users who will access it to access ANYTHING else in the backend except for this component.
I tried following these two instructions:
http://www.aclmanager.net/blog/general/31-how-to-add-basic-acl-support-to-your-extension
http://docs.joomla.org/Developing_a_Model-View-Controller_%28MVC%29_Component_for_Joomla!1.6_-_Part_14#Describing_the_ACL
I made a new User Group with a parent of public and allow admin login (which would lock them out of everything) and then tried adding the ACL code from those links above with permissions to create and edit but I just get a blank screen (not even a logout link). The "Debug Permissions Report" showed the correct permissions but nothing's showing up.
Any ideas? My next step is to manually go through every component and not allow access to that new User Group but it seems like there's an easier way.
Thanks!
In Joomla! 2.5 we regularly create "Content" only backend users that have access only to the 'com_content' component.
Going back through our steps the only thing you haven't specified is adding the new user group to a View Access Level. If you're using the standard sample content installed when setting up a Joomla! website you can add your new user group to the "Special" view access (although any will do).
If a new group has 'admin login' privileges it can login but without a View Access level it can't see anything.. it's a subtle difference but it's the way Joomla! works.

Change built-in webserver to use 'Index.aspx' as default page

When I run my application on localhost I get a directory listing and have to click on 'Index.aspx' to view the page.
I have already set the Set As Start Page to 'Index.aspx', which means when I press 'F5', 'Index.aspx' is opened.
This works fine, but when navigating through the site, if there is a link, such as '/FolderName', I get a directory listing, and have to manually change the URL to '/FolderName/Index.aspx'.
I believe this is because by default, the default page is 'Default.aspx'?
Is it possible to change this to 'Index.aspx'? It would save me a lot of time!
AFAIK this is not configurable. Your best option would be to rename all your index.aspx files to default.aspx. See the following link with an accepted answer to back up mine. Have fun with your renames :)
asp.net application default file Index.aspx

Magento Admin login kicks me out back to the Admin login

After I enter my username and password and click "Login" it sends me back to the Login page with NO error messages. The URL changes to include a session key and that's it. Everytime I click Login again, the session key is regenerated and I still can't log into the admin interface.
I just encountered this problem on one of my servers (not a localhost installation). Turns out the system account was over quota, so I presume Magento was unable to create the necessary temporary files. (I noticed this when trying to create a directory on the server over ssh.)
So... maybe check to make sure the account under which Magento is running isn't over quota on your server? At the very least, it might not be a Magento problem directly.
Clear the contents of the directory var/cache and try again.
If that doesn't help check the table core_config_data in the database for records with a path value of "web/secure/base_url", "web/unsecure/base_url" and "admin/url/custom". These should match the page you are trying to log into (but without "index.php/admin/" at the end)
Finally check your browser's cookie settings and that the server's PHP is able to set cookies.
I was having the same problem running Magento 1.5.1 on my production server. I would log in to the admin, the url would show the address for the dashboard (with the secure key), but the screen would still be the login screen. There was no error. This happened with FF, Safari, and Chrome.
I fixed it by manually setting two core_config_data values in the database. They are as follows:
web/cookie/cookie_path = /
web/cookie/cookie_domain = "mydomain.com"
clear out var/cache and try to log in. For me, it worked.
Version 1.7.0.2 I have been moving my magento store from on server to another one, and I had the same problem. Use phpamdin to edit your database on new server, search for web/cookie/cookie_domain in 'config path row', the value is probably your old domain name: yourdomain.com, change that to your new domain name OR to your new IP address (new server). If you attend to use your old domain on new server environment you will probably want to set your story ready before you switch your name servers. That was the case for me, after I added my new server IP to web/cookie/cookie_domain instead of domain I was finally able to log into my magento backend.
I had some problems when on a local server. It was on http://server/username/ and so didn't have dots in it. If we changed the settings to be the IP address of the server then it was fine.
There can be several things that cause this behavior. This is my checklist. One of them will eventually fix it.
Click the "forgot password link" and then the "back" link. This will remove any possibly misplaced params in the URL as well as make sure you're on the right server (some installations have separate admin servers)
Clear cookies or use an incognito window
Try another browser
Local installations: Try using 127.0.0.1 instead of localhost (and update the base URL in the core_config_data table)
Clear Magento cache, full_page_cache, and session directories in the magento/var/ directory (and repeat 1 and 2)
Truncate the core_session table
Verify your Magento has correct memory settings
Check Magento system.log and exception.log files and debug
Check PHP's error logs and debug
I've experienced this issue using Opera, while in other browsers it worked fine.
Also, make sure to set correct cookie options in:
System > Configuration > Web > Cookie Settings
Also, make sure that your system time / time zone on the server and php and magento match up.

Resources