To control what user groups have access to an offline site, go to Global Configuration (System -> Global Configuration) and select the Permissions tab. Select the user group you want to give access on the right hand side (in this case "Registered"), and set Offline Access to "Allowed". (Default setting is "Inherited", thus Not Allowed. Save. Your registered ...
There are 2 options to prevent this:
One is a global setting to stop this from happening.
In Global Configuration -> Site Settings -> Mouse-over edit icons for:
We can set this setting to Modules & Menus, Modules, or None.
The other option is related with the Module Permissions. Since in Joomla 3, we have the ability to set permissions by module, we ...
Just my 2 cents as there could always be some other issues.
In regards to permissions, it's not always the chmod levels that need changing. It may sometimes be due to the directory group permissions. Changing the the group permissions can be achieved easily through SSH with a tool such as Putty and the following command:
Yes it will.
Instead go to:
Click the tick box to tick all article.
Then click 'Batch' up the top.
To Move or Copy your selection please select a Category.
Select your new category, make sure 'Move' is selected and then click Process.
This will do it all for you and update the relevant category ...
I got a similar issue. Maybe my solution will help you.
I was not able to edit a second time my article and I was also receiving this message : You are not permitted to use that link to directly access that page (#article-id). The error was not appearing when my browser extension « Cache Killer » was activated and the same thing was going on with the mode ...
It proved to be a permissions issue. As always Akeeba Admin Tools come in handy in such issues. I installed it, configured the permissions settings and applied the fix permissions feature.
Tried to install again the update and this time it went smoothly and completed.
This answer solved my issue - but @Lodder's answer provides a few additional ...
I found the answer my self in a SEBLOD blog entry. There is a small arrow at the right corner of the content types main settings.
When opened there is a permission button:
And in there I could set the Create permission for the group Public to Allowed.
If I understand your problem correctly, what you need to do is create a top level page for your private news blog - an actual menu item for category blog. Then you can control what modules and url those articles get when clicked on, and keep it's users restricted to private.
ACL is an intermediate topic (at least) and if someone needs to create a more complicated ACL configuration, needs to have a solid base of relevant knowledge and past experience. Experience can be gained by working with simpler ACL setups at first, and going to more advanced and complex setups as long as someone understand how things work.
It's not easy to ...
The files should be owned by your FTP user, which may be root for you if you are setting up a dedicated server manually.
The entire goal of the article was to allow you to still be able to change the files, with "you" in this case expected to be someone accessing a shared host over FTP. You're not expected to have root access to the server.
Try Advanced Template Manager by NoNumber
With Advanced Template Manager you have the possibility to assign template styles to just about anything you want (URLs, OSx, User IDs, Browsers, Tags etc..). However it's not compatible with T3 or Gantry FW.
You may have to go for the pro version for all the features but I can highly recommend these extensions. ...
My guess is more that the "last" SuperUser is unknown. It shouldn't be possible to deactivate/delete that one. Don't want to test it right now. The SuperUser has hardcoded permissions.
You can check this
'#__usergroups' : id 8 exists
'#__user_usergroup_map' : at least one group_id 8 should exist
'#__users' : find the user to log in with.
If you don't ...
It's still hard to believe how this user was able to remove Super Users permissions - it really takes some efforts to achieve this. Again are you sure this is the case ? Are you getting any special message when trying to login?
It can be just that he disabled some plugins.
I would suggest first to check with PHPmyAdmin in the extensions table to see if the ...
Joomla stores all the access permission rules in #__assets table.
There is a field rules in #__assets table which contains permission value, so you need to update the table with your values.
I have not done such changes directly in database before so don't know what exactly you need to put as default value.
Refer this link for understanding access ...
We have a feature called Access Control List (ACL), with this
you can create a user groups and assign them permissions to
access, create, edit or delete content or modify certains parts
of your site like articles, categories, modules, global configurations, etc.
For example, we have the user group "Author", in the screenshot you can see a
category called "...
Add a simple access.xml file in your administrator component directory (administrator/components/com_joocommerce) and you can configure permissions for your component.
<?xml version="1.0" encoding="utf-8" ?>
<action name="core.admin" title="JACTION_ADMIN" ...
This is usually a directory permissions issue with the tmp folder.
When installing extensions, the tmp folder is used by the extensions installer, to extract the uploaded archived file. Therefore, the folder needs to exist and be writable.
A good place to find out if your Joomla folders are writable is by checking in the:
System Information -> Directory ...
In ChronoForms v5, edit your form, go to the Setup tab and drag an "Authenticator" action into the appropriate event in your form:
Edit the Authenticator properties to set the required permissions:
You can then drag appropriate actions into "On Success" or "On Fail" as appropriate.
For example, you might drag a "Display Message" action into the "On Fail" ...
It well could be a cache problem, Joomla by default does not cache pages when logged in precisely because of such issues.
Mainly adding an answer to note that Apache can be set to cache only specific extensions, so it should be set to cache only extensions for images, scripts, and fonts. This will still occasionally cause issues and will not add performance ...
1. Edit State Privilege
In order for a user to be able to set/switch the publishing status of a content item (published/unpublished etc), they need to have the Edit State permission assigned on them.
2. Core Usergroups
From the core front-end usergroups, only the Publisher has this kind of permission. So only users of that usergroup can set / ...
To set files and directories to chmod 777 or even chmod 770 is not a good idea on a production system.
Every webserver system like apache2, nginx can be configured to work with a special user and group - that's important not to get any user rights on the system. On most Debian like systems, the user is set to www-data with group www-data, standard is the ...
By default, the file permissions on Joomla extracted files are 644 and the folder permissions are 755.
If you're seeing something different, then, as @jdog mentioned above, you will need check your umask settings (if you have a system administrator then I suggest you let him handle this). umask is used to remove deny default permissions (it is not used to ...
You are probably an Administrator and not the Super User, you can check your account at Users->Manage, that's why you don't have access to all Joomla functions.
You can try to manually update Joomla follow this (not really sure if an Administrator even can) but i think that up the road you 'll need full access to make your life easier.
I realise that this is a bit late but …
Yes, it is possible for extensions to define their own permissions, as really the "permissions" are fundamentally just strings. However, the standard method would be to use the extension's access.xml file you describe above. The steps would be:
Define your permission in the access.xml file (you would generally have ...
I have been meaning to provide an update for some time. I solved this problem with two pull requests to CiviCRM a few months ago. My memory is fading, and I might have some of the Joomla terminology wrong -- edits welcome.
The first pull request makes changes to the component (i.e., the Joomla parts). Basically, instead of using the rules form field type, I ...
A 403 error denotes that the operation/task is not permitted. This is usually comes from strict permissions, or security settings posed by the server e.g. a firewall, or it can be due to file permissions.
From your updated information, my guess is that the 403 error you are encountering comes from a software firewall - it could a Joomla extension like the ...
Yes you do need to check the permissions in your Ajax-handling code.
The way you would do this would be to follow the pattern in the Joomla MVC FormController, where it uses the Joomla User authorise method, eg, to check if a user can create an article:
$user = Factory::getUser();
authorise() returns true ...
Just assign the users to the basic registered user group and in your login module and or menu item it will allow you to choose a redirect after successful login and logout. Simply choose the page your are referring to.
You can give to an author the power to publish immediatly an article :
ARTICLE > PArameters > Right
for Author : turn "Change the status" to allowed (no Disallowed)
Then when an author create an article with the frontend, his status is immediately "allowed"