inherit
133146
0
Jan 7, 2024 2:07:03 GMT -8
Alanna 🥀🖤
3,564
November 2008
alannab
|
Post by Alanna 🥀🖤 on Aug 27, 2014 14:56:27 GMT -8
Like Plugins, I would like to request/suggest there be an option to disable editing of the Theme by anyone but yourself (the author). Therefore, if another user uses said Theme, they cannot remove the author's credits, ruin their designs, etc. The only place in which they can go and make their changes would be the Colors & Theme Creator and Visual Editor so they can change colors, images, banner height, forum width, etc. Of course that would mean that authors would have to go into detail with the Visual Editor Builder to enable users whom are using it to edit it to their wishes, however, I believe that is an appropriate cost for having that Theme locked to just the author.
Because users have to go into some Layout Templates to be able to add their information within tables and such, there could also be an option to disable certain Layout Templates and have others open so other users to edit.
I hope that made sense? I just think there should be some sort of option for Theme Creators since Proboards protects Plugin Creators work already but there is no protection for Theme Creators.
Thank you for reading and considering!EDIT! See this post for edited and revised request.
|
|
#e61919
Support Manager
154778
0
1
Apr 27, 2024 23:19:00 GMT -8
Michael
19,550
May 2010
wiseowl
|
Post by Michael on Aug 27, 2014 15:35:44 GMT -8
Hi,
One of our rules that we always try to live by here at PB is "Never implement functionality that would take functionality away from users" (users generally being administrators). From your perspective I do see how it seems unfair that we would be "protecting" plugin creators but not theme creators. However, us "locking" plugins to a specific creator does not remove functionality from the end user at all. Locked plugins interact with other plugins for example. There isn't anything that we've taken from the end user.
Even if we were able to lock templates (and themes) in a satisfactory way, we couldn't hide the source, or be able to make it so that the CSS can't be loaded without breaking a lot of other stuff. Us adding new variables to the template would mean that theme creators would have to go and update every theme that they've made, and subsequently would mean that all of the users of those themes would have to update their themes as well. It just wouldn't be feasible.
Something we could consider would be making a non-editable field that credits the author with the creation of the theme! We're open to suggestions but the process of locking down themes to be un-editable isn't something that we have plans of implementing.
|
|
inherit
133146
0
Jan 7, 2024 2:07:03 GMT -8
Alanna 🥀🖤
3,564
November 2008
alannab
|
Post by Alanna 🥀🖤 on Aug 27, 2014 15:50:05 GMT -8
Anything that is even similar to protecting theme creators like there is for plugin creators that you are willing to do, please put into the future feature list. What I described above is just what I personally believe is the best feature to have implemented into themes from day 1, however, all well.
Also- I want to note that I do believe locking plugins do limit users because I don't use many plugins because of it. I can't style them correctly to match my forum because it is locked and there are no proper classes coded into the plugin so I can't just add a style in my style sheet either.
|
|
#e61919
Support Manager
154778
0
1
Apr 27, 2024 23:19:00 GMT -8
Michael
19,550
May 2010
wiseowl
|
Post by Michael on Aug 27, 2014 15:56:56 GMT -8
I'll flag this thread as a feature request then. As for the lack of classes coded into the plugin, that's something that should be brought up and discussed with the plugin authors themselves. I believe that most (perhaps many, if not all) plugin authors would be willing to add classes or provide a class list so that plugins can be styled easier. Plugin authors and theme authors rely on each other so its natural that both would want to provide the best to each other!
|
|
inherit
133146
0
Jan 7, 2024 2:07:03 GMT -8
Alanna 🥀🖤
3,564
November 2008
alannab
|
Post by Alanna 🥀🖤 on Aug 27, 2014 15:58:39 GMT -8
Alright and thank you.
|
|
#e61919
2
0
1
Mar 22, 2024 12:10:09 GMT -8
Martyn Dale
$[user.personal_text]
20,088
February 2003
martyn
|
Post by Martyn Dale on Aug 27, 2014 16:26:13 GMT -8
Another consideration might be to state the benefits of correct classing somewhere in the plugin development area. I am sure many just never consider it rather than not wanting to add it, and the benefits would be pretty wide reaching.
In terms of how the themes work, something to the degree you want wouldn't really be viable, for many reasons including those stated by Michael.
With that said, while it is not on the immediate roadmap, we do have plans for ways to expand the functionality of the template engine itself. One of these plans to allow insertion of custom child templates. An example of a child template would be the miniprofile. The miniprofile can either be inserted as a single [$miniprofile] variable, or its contents can be explicitly listed.
The child templates would operate much the same way as existing ones (such as the miniprofile) in how they also execute the template code rather than treating it as fixed HTML. In that situation, I would see a benefit to allowing those child templates in a plugin.
This way all of the code could be in a protected plugin, but would work much the same as a template. The degree of how wide reaching the child templates are would be down to the author at that point.
While it wouldn't completely take away the ability to edit templates, it would create a very literal separation between the inserted components of a theme, and the rest of the template engine. This wouldn't be out of line with our policy, as it would be allowing functionality to be taken away, its just never giving access to some things to begin with.
Of course a larger system change like that will be further afield than a smaller change such as thae one suggested by Michael.
|
|
inherit
194160
0
Mar 23, 2015 9:54:45 GMT -8
blc
2,641
May 2013
blc
|
Post by blc on Aug 27, 2014 18:32:33 GMT -8
Anything that is even similar to protecting theme creators like there is for plugin creators that you are willing to do, please put into the future feature list. What I described above is just what I personally believe is the best feature to have implemented into themes from day 1, however, all well. Also- I want to note that I do believe locking plugins do limit users because I don't use many plugins because of it. I can't style them correctly to match my forum because it is locked and there are no proper classes coded into the plugin so I can't just add a style in my style sheet either. A way to prevent credits from being removed would be nice. Maybe a section like the description area could be locked so that credits could not be removed?
|
|
inherit
133146
0
Jan 7, 2024 2:07:03 GMT -8
Alanna 🥀🖤
3,564
November 2008
alannab
|
Post by Alanna 🥀🖤 on Aug 27, 2014 18:34:16 GMT -8
I honestly have no idea where you are going with that. Not sure how that helps with my suggestion at all actually. Care to explain how it would in detail? From my understanding of the child variables, they can still be removed, therefore, not very secure. Let me go into more detail as well with what my personal issues with theme creating are: - Obviously, whatever credit we add can be deleted.
- Users mess with the HTML within the layout templates or CSS within the Style Sheet trying to change a color or image, ruin it, and then ask me to fix it. Or, "why isn't your theme working right?"
- Users steal my work- either the entire theme by replacing my credit with their own or completely removing it (see issue I.), or by taking parts of the theme layouts and pasting it on their skins like the Board Remodel, Mini Profile Remodel, etc.
Those are the MAIN issues that I deal with. While many people tell me I should be "flattered" that people want to take my work and use it... I'm not because I am making these for free and providing them for free. It shouldn't be hard to ask for some credit/recognition which ALL plugin creators get because their credit and hard work cannot be messed with unless they allow it to. Don't get me wrong- not trying to complain and throw a fit because I love creating themes and I love providing them (that's why I run a resource forum). I would just LOVE it if there was some way to protect theme creator's work if possible. Even if it's just a place to put credit that can't be removed (preferably a way to be able to put the credit anywhere on the forum and have it untouchable). I know there is no way to keep people from right clicking, viewing the source, and taking the raw coding though. No way around that unless you disable right click (which by the way, is that against TOS?), but thank you again for reading and considering.
|
|
inherit
133146
0
Jan 7, 2024 2:07:03 GMT -8
Alanna 🥀🖤
3,564
November 2008
alannab
|
Post by Alanna 🥀🖤 on Sept 7, 2014 10:17:43 GMT -8
Casual bump?
|
|
#eb7100
33409
0
1
Apr 14, 2024 15:59:10 GMT -8
Brian
48,129
November 2004
smashmaster3
|
Post by Brian on Sept 7, 2014 10:21:40 GMT -8
No need to bump a feature request. The devs look through them from oldest to newest pending whether or not we're even looking for features at the moment.
|
|
inherit
133146
0
Jan 7, 2024 2:07:03 GMT -8
Alanna 🥀🖤
3,564
November 2008
alannab
|
Post by Alanna 🥀🖤 on Sept 7, 2014 10:24:23 GMT -8
I wanted a response to my last post.
|
|
blueshead
Full Member
More hot peppers please!
Posts: 928
inherit
185994
0
Jun 17, 2018 15:20:52 GMT -8
blueshead
More hot peppers please!
928
November 2012
mrblueshead
|
Post by blueshead on Sept 7, 2014 10:36:55 GMT -8
" No way around that unless you disable right click (which by the way, is that against TOS?), but thank you again for reading and considering."
Not sure about this.. Todges Plug in "Image Security" disables right click so people can't d/l photo's.. Of course it's easy to get around..
|
|
inherit
133146
0
Jan 7, 2024 2:07:03 GMT -8
Alanna 🥀🖤
3,564
November 2008
alannab
|
Post by Alanna 🥀🖤 on Sept 7, 2014 10:44:49 GMT -8
" No way around that unless you disable right click (which by the way, is that against TOS?), but thank you again for reading and considering." Not sure about this.. Todges Plug in "Image Security" disables right click so people can't d/l photo's.. Of course it's easy to get around.. You can get around anything if you really know how- the point is some people won't bother taking that extra step.
|
|
inherit
The Great Cinnamon Roll
191518
0
Oct 19, 2016 22:17:44 GMT -8
David Clark
Care for some tai chi with your chai tea?
17,602
March 2013
davidlinc1
|
Post by David Clark on Sept 7, 2014 10:56:41 GMT -8
Disabling right clicking is not against the ToS as far as I know, but in my personal opinion it's definitely pretty annoying to the average web browser (and will not stop the truly dedicated image thief from downloading the images in other ways).
@khristian, to get your credit in the theme and make it difficult to remove, why not hide this CSS somewhere deep in your style sheet?:
footer:after { content: "This theme created by Trinity Blair"; }
This will place the text just under the footer on all pages, and even when looking at the text using the browser inspector it's a bit difficult to determine how/where the text is coming from. Anyone can edit HTML, but text being generated via CSS is not really the first thing that jumps to someone's mind. I think you'll find your signature won't be removed from as much of your work if you include that.
|
|
inherit
133146
0
Jan 7, 2024 2:07:03 GMT -8
Alanna 🥀🖤
3,564
November 2008
alannab
|
Post by Alanna 🥀🖤 on Sept 7, 2014 11:07:08 GMT -8
Disabling right clicking is not against the ToS as far as I know, but in my personal opinion it's definitely pretty annoying to the average web browser (and will not stop the truly dedicated image thief from downloading the images in other ways). @khristian, to get your credit in the theme and make it difficult to remove, why not hide this CSS somewhere deep in your style sheet?: footer:after { content: "This theme created by Trinity Blair"; }
This will place the text just under the footer on all pages, and even when looking at the text using the browser inspector it's a bit difficult to determine how/where the text is coming from. Anyone can edit HTML, but text being generated via CSS is not really the first thing that jumps to someone's mind. I think you'll find your signature won't be removed from as much of your work if you include that. I have done similar things but it didn't help, like you said it won't truly stop the dedicated users. Also- I'd like to be able to place my credit anywhere on the forum since depending on the design, I may put it within the banner, the bottom of the forum, a side table, etc. Not only that but I like styling the credit as well and adding links. That does not allow that to my knowledge.
|
|