I’m running EE3 (core). During installation, I renamed and moved the system folder outside the public_html (webroot) folder. Everything has been working well until tonight when I added a plugin for social sharing.
Everything installed correctly and I can access the settings via the Addons Manager. However, the images, css, etc for the plugin are returning 404 errors. When viewing the source, the path it is using for the images is the default path of EE (public_html/system/user/addons/…).
What should I do to resolve this and avoid issues in the future when installing other addons?
For those who may stumble on this in the future. The answer to my problem was to create a 301 redirect on the assets folder provided with the addon. What I did exactly was as follows:
RedirectMatch 301 /system/user/addons/simplified_social_share/(.*) http://domain-name.com/path/to-new/destination/$1
All works. However, after all the trouble, I don’t think I’m going to use the addon. Lol. At least I learned something. Hopefully this helps someone else in the future.
Worth noting, the developer never got back to me.
I got it from devot.ee, which can be found here Simplified Social Sharing. There’s a link on there (in most cases) to the developers site.
I should also mention that the add-on didn’t work perfect. You can choose horizontal or vertical buttons. However, although I choose horizontal, they both showed up on my site. The horizontal was where I placed the tag and showed the icons that I chose in settings. The vertical was on the browser right edge and didn’t show the correct social site icons, according to my settings. Also, it adds a ‘More’ button, which creates a strange popup when hovered/clicked. Personally, that bugged me.
In both cases, I found the tag class or id and changed display to none in my css file.
I am still exploring other options, but I do currently have it installed on my site (which is still under construction). It does seem to do the job.
When you read the comments below, it actually mentions your issue:
The add-on works ok, but I had to hack it to get it to work in my environment, as it hard-codes folder names. So be aware if you have renamed your system folder, you will need a redirect or hack for this to work properly.
This issue seems to remain unfixed since 2014.
When you read the comments below, it actually mentions your issue:The add-on works ok, but I had to hack it to get it to work in my environment, as it hard-codes folder names. So be aware if you have renamed your system folder, you will need a redirect or hack for this to work properly.This issue seems to remain unfixed since 2014.
Wow… Guess I should have read those a bit more thoroughly. If it would have had the actual solution, I’d really be hating on myself right now. Good catch.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.