You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was discussed before (#64), but I wonder why there is no improvement yet: When Fansoro is downloaded, unpacked and uploaded via FTP, then an error message appears in the browser that a file vendor/autoload.php could not be found.
Only if you install Fansoro via Composer, after you have installed Laravel via Composer, as far as I know, this directory will be created. But this is very uncomfortable in my opinion. It should be possible, as an alternative, to simply upload a CMS via FTP onto the web server without caring about frameworks and what could be missing. It might be quite usual for developers to use Composer or whatever tools, but not for end users, not even for webdesigners like me.
The text was updated successfully, but these errors were encountered:
@laleveille: Thank you, I downloaded that version and will give it a try. The development of Fansoro seems to be stuck; hopefully the project is not dead, I like this CMS.
This was discussed before (#64), but I wonder why there is no improvement yet: When Fansoro is downloaded, unpacked and uploaded via FTP, then an error message appears in the browser that a file vendor/autoload.php could not be found.
Only if you install Fansoro via Composer, after you have installed Laravel via Composer, as far as I know, this directory will be created. But this is very uncomfortable in my opinion. It should be possible, as an alternative, to simply upload a CMS via FTP onto the web server without caring about frameworks and what could be missing. It might be quite usual for developers to use Composer or whatever tools, but not for end users, not even for webdesigners like me.
The text was updated successfully, but these errors were encountered: