Warning Improvements by Xon

Warning Improvements by Xon 2.11.6

No permission to download
@Mr Lucky Can you verify if those phrases have any contents via the AdminCP => phrases section?

If they do, can you add a space to the text and click "save" then remove it and click save again?
 
warning_title.11 is fixed when I edit the warning as you suggest.

But I don't have any categories, the one at the top (sv_warning_category_title.1) is not there when I disable the addon.
 
But I don't have any categories, the one at the top (sv_warning_category_title.1) is not there when I disable the addon.
You'll need to edit the warning category, update the title and then save it.

Would it be possible to have View own warnings permission based? Thanks.
I'm currently focusing on porting my paid add-ons, so this would be a low priority.
 
But I don't have any categories
The add-on automatically creates one called "Warning" when you install the add-on, and then assigns any warnings to it. This url path should let you use it; /admin.php?warnings/category-edit&warning_category_id=1

If the row is really gone, you'll need to manually re-add it by running this SQL;
Code:
INSERT INTO xf_sv_warning_category (warning_category_id, parent_category_id, display_order, allowed_user_group_ids)
VALUES (1, NULL, 0, 2)
 
Ah, OK I didn't know it would create a category called warnings. I've edited the phrase and called it warnings all fine now thanks.
 
It seems that if I have options set so users cannot view their own warnings, if they click on an alert they get an error page.

Obviously the alert in this case cannot link to a warning, but in that case it would better if users got a more useful message other than Ooops We ran into some problems.

Alternatively it could work if users can be prevented from viewing their warnings in their profile, but only be able to view their own warnings when it is an alert.
 
Obviously the alert in this case cannot link to a warning, but in that case it would better if users got a more useful message other than Ooops We ran into some problems.
It should give a permission denied error, not an "oops we ran into problems". I'll look into that this weekend.

I'll probably have it remove the link if there isn't any permission.
 
It should give a permission denied error, not an "oops we ran into problems". I'll look into that this weekend.

I'll probably have it remove the link if there isn't any permission.

Yes, no link at all would be fine
 
Back
Top Bottom