access level warning message in File edit view

More
9 years 2 days ago - 8 years 11 months ago #65849 by manchine
When opening a file in edit view, a strange warning message is showing:

Access level: 0 is not valid. Setting Access level to 'Public'. Please select a new access level and save the record.

It is still possible to save the record. However, I'd like to know where the '0' access level value comes from.
Last edit: 8 years 11 months ago by ggppdk.

Please Log in or Create an account to join the conversation.

More
9 years 2 days ago #65851 by micker
your joomla and flexicontent version ?

FLEXIcontent is Free but involves a very big effort on our part.
Like the our support? (for a bug-free FC, despite being huge extension) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing reviews. Thanks![/size]

Please Log in or Create an account to join the conversation.

More
9 years 2 days ago #65853 by manchine
Joomla 3.6.5
FC 3.1.1

Thanks!

Please Log in or Create an account to join the conversation.

More
9 years 2 days ago - 9 years 2 days ago #65856 by ggppdk
Hello

This is not a bug, it is just a notification that :
- the file has a non-existing access level

Select a valid access level and save the form

----
It would be a bug only if :
you have added the file --recently-- and you added it with a valid access level e.g. public
and the access level was lost,

otherwise as said above , select an existing access level and save the form


-- Flexicontent is Free but involves a big effort on our part.
Like the our support? (for a bug-free FC, despite having a long list of functions) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing with a 5-star review. Thanks!
Last edit: 9 years 2 days ago by ggppdk.

Please Log in or Create an account to join the conversation.

More
9 years 20 hours ago #65890 by manchine
Hmmmm... Bug or no bug, the fact that 0 is showing up in the Access Level select list is definitely weird.

Please Log in or Create an account to join the conversation.

More
9 years 12 hours ago #65894 by ggppdk
Hello

it is much better than ... the file just not showing in frontend without any warning because of bad access level


-- Flexicontent is Free but involves a big effort on our part.
Like the our support? (for a bug-free FC, despite having a long list of functions) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing with a 5-star review. Thanks!

Please Log in or Create an account to join the conversation.

More
9 years 1 hour ago #65896 by manchine
It still remains to be explained why the error happens, even if not functionality is affected at this point.
Up until 3.1.1, the warning message and the mysterious access level 0 did not show up.

Please Log in or Create an account to join the conversation.

More
8 years 11 months ago #65898 by ggppdk

Up until 3.1.1, the warning message and the mysterious access level 0 did not show up.


Exactly, it was added by v3.1.1, and it is intentional for the reasons explained previously

If newly created files do not have access level zero, then were are good here


-- Flexicontent is Free but involves a big effort on our part.
Like the our support? (for a bug-free FC, despite having a long list of functions) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing with a 5-star review. Thanks!

Please Log in or Create an account to join the conversation.

More
8 years 11 months ago #65903 by manchine
As I've mentioned in an earlier post, the *existing* files where the warning message is showing already had the access level correctly set to Public.
I still think that the behaviour described in my opening post is not supposed to happen.

Please Log in or Create an account to join the conversation.

More
8 years 11 months ago #65945 by ggppdk

I still think that the behaviour described in my opening post is not supposed to happen.


The message was added because the file was not showing in frontend and users could not understand why it is not showing

The reason that file has this access level ?
Maybe because of upgrade from J1.5 or because of older FLEXIcontent bug that saved it with access level ZERO


-- Flexicontent is Free but involves a big effort on our part.
Like the our support? (for a bug-free FC, despite having a long list of functions) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing with a 5-star review. Thanks!

Please Log in or Create an account to join the conversation.

Moderators: vistamediajoomlacornerggppdk
Cookies user preferences
We use cookies to ensure you to get the best experience on our website. If you decline the use of cookies, this website may not function as expected.
Accept all
Decline all
Essential
These cookies are needed to make the website work correctly. You can not disable them.
Display
Accept
Analytics
Tools used to analyze the data to measure the effectiveness of a website and to understand how it works.
Google Analytics
Accept
Decline
Save