Posts by ElyD

1 post
  • Has been part of the Envato Community for over 1 year
ElyD says

I like the fact that you have to follow proper naming standards and the like, but some of phase 2 is distinctly worrying…

1) What about fonts like fontawesome – that is licensed to “theme developers”, not plugin developers. So therefore I assume I won’t be able to load up fontawesome within this ‘separate plugin’. While that isn’t a problem if they use my theme and plugin, it will become a problem if the shortcode is in the plugin and they change themes to a theme that doesn’t load up fontawesome (or whatever other symbol font the shortcode works off)....

2) What about themes from elsewhere, or existing ThemeForest themes – if my ‘separate plugin’ has a custom post type or shortcode with the same name, it’s going to create an issue when they swap to that theme, because even if the custom post type is called the same name it’s extremely unlikely that they contain identical meta data fields. So to prevent this we’re all going to have to name our shortcodes and custom post types with unique identifiers and then the users are eventually going to end up with loads of different plugins they HAVE to keep loaded that slows their site down to an unusable crawl.

by
by
by
by
by
by