"This section is currently offline"

Is this happence when you access article full view or artilce list? What is access level of the article if you check in in DB?

Hello,

Sorry for delay.

I've just checked out the DB. Access level is set to 1 (Public). It happens on full view.

Regards.

Is article inside category? If yes what is category access?

Article is not in category :+(

Give me access I'll have a look.

Hello Sergey,

I've just found the problem. Actually, the Access level of Section was set to Registered... did not pay attention to this setting. Every thing is fine now.

Thanks for fast support.

Just out of curiosity:
If the section access is "Registered", why did it show the message "This section is currently offline"?
Actually the wrong wording. Or language constant!?

pepperstreet If the section access is "Registered", why did it show the message "This section is currently offline"?

Actually the wrong wording. Or language constant!?

This is taken from Joomla's "Site is offline" idea.

Sergey This is taken from Joomla's "Site is offline" idea.

But this is a total different use case and context, IMHO.
The section is not offline.

It should either display a message that talks of something like:
"you can't access..."
"you don't have the needed privilege..."
"you don't have the rights to..."
"Access denied!" ;) (maybe too little information for the DAU)

Or something like a positive advice, that explains the reason to the visiter.
This might prevent support emails and further questions... :
"You have to be ACL to access this section"
"You need the following access rights to view this section: ACL"
etc.

There are to many scenarios to hame message for each. That is why along ith section access you can ener message. So you can enter there whatever you want acording to your site context.

Sergey There are to many scenarios to hame message for each. That is why along ith section access you can ener message. So you can enter there whatever you want acording to your site context.

Maybe I was lost in translation ;) The issue description implied a "wrong" message for the section access. That's why I made the previous suggestions.

Anyway, I have tested the access restriction message, and the wording is o.k.

Although a red Error seems to be a bit harsh to me. An error might confuse the average user. A positive info, notice or warning might be the better choice for best user-experience.

This is how JError behaves. I use somethign liek this.

JError::raise(E_WARNING, "Text")

But it set it to error anyway. Also JError is depricated and I have to refactor anyway.