I have downloaded TastyIgniter from GitHub and running it in localhost (Windows with WAMP and PHP version 7.1.9). In the last step of installation, I am getting errors that "Downloaded files from server are corrupted" and "Missing vendor files". May I know what is causing these errors and how I can run it without bugs in my localhost.
Run composer update command in the root of your project.
If composer is not installed. Download it from this link official website.
it seems like they hardcoded something.
when you unzip the setup-master folder, keep it as it is and don't rename or move its content.
start your installation by calling:
yoursite/setup-master/setup.php
this worked for me.
I tried to run the installation previously by unzipping the files directly in my html folder and tried several fixes but no success.
after a successful installation you need to forward in your apache config / .htaccess file to the subfolder
In order to do so, don't forget to perform the Post-Installation steps mentioned here:
https://tastyigniter.com/docs/master/installation
I finished by aborting tastyigniter. After a successful installation and theme activation, the application worked fine then "suddenly" it throws an exception that the newsletter component can't be found. All suggested helps on the dev forum didn't help. Even after reinstalling the application it comes to the same error.
Apparently you won't come over a "professional" installation support by the developer ($$$)
Thats pretty much my experience, I tried to install in different servers and environments running into several issues, especially it seems not to be made for anything other but specific development environment. Trying to secure installation with SSL already is an issue, that is very standard but poorly documented with this project. Having an example of how configuration files nginx go! Pay or have an experienced server admin do the trial and error. Integrated update mechanism, get your staging server and help to code. It is ok, just would be more honest to mention upfront, that running that app in production environment requieres some serious server administration skills and is nothing like installing and maintaining a wordpress or any other mainstream script.
Related
At work we took back our existing store running on Magento 2 from an external development agency. I need to get the project running in local development (with docker).
I familiarized myself with a vanilla project from the official docs and managed to get it running by downloading the vanilla template with composer, granting the proper permissions on files and folder and running the magento setup:install command.
My question is how do one goes when kick starting from an existing (production running) project?
Do I need to run setup:install again? If I do, why?
What do I need to import from production to ensure any content or configuration created via the admin is also running on my local setup? Should I import the complete Database from production?
I know our setup is using more than just php and mysql, but env.php seems to be listing only db configuration and admin url. Where can I get the complete service configuration informations about what our setup uses?
Anything else I am missing to get started with an existing project for local development?
As someone who is running Magento 2 on a local environment myself, hopefully I can shed some light on this.
If you have a direct copy of the live site, you do not need to run setup:install again.
Ensure you have a copy of the entire Magento 2 site (you can technically ignore the vendor folder, as you can run composer install and it will redownload those files, but that's up to you). Also get a copy of the entire database. Magento 2 is notorious for copying the same data to multiple tables so something could break if you don't have everything.
What do you mean by "service configurations" If you are referring to Magento 2 extensions, that data is saved in the database, not the env.php file. env.php is only for server side configurations, such as the DB information, Caching, and things of that nature. On mine, I use Redis for site Cache, so that would be included in that file as well, as an example.
When you first unpack the site to your local environment, run composer update in the directory. This will ensure you have all the proper files installed. If you are going to run a local dev environment, set the mode to development with the following command: bin/magento deploy:mode:set developer. This will allow you to make changes and to view those changes by just refreshing the page, rather than flushing cache all the time.
All queries are replied correctly by Eric. I am also not sure about "service configurations" you have mentioned here. If this is about third-party extensions/services you can check config.php file for this.
I have installed Moodle 3.7.1 with XAMPP. The installation had been successful and problem-free. I followed the below video for installation:
https://www.youtube.com/watch?v=Ov2dGoOBmSI&t=436s
Now my main objective is moodle plugin development. Since I am relatively new to this I was exploring plugins and trying to build a simple one first.
But whenever I am trying to install plugin (my own or from Moodle directory) I receive the SUCCESS message but then get 'Page Loading Error' and thereafter I am not able to go to any page
I found this thread on Moodle forums and have tried most of the solutions they offered.
https://moodle.org/mod/forum/discuss.php?d=355930
I dont wish to work on older XAMPP version
My cache folder under Xampp's moodledata folder is empty and i tried clearing my browser cache and restarting the servers.
But the issue still persists
Any ideas what maybe causing this? I have a feeling that its some kind of configuration issue but I dont know where to look and what to look for.
Thanks for all the help. It took me alot of installation and uninstallations but finally when I downloaded the full Windows installer package--it worked.
I guess it was some kind of deeprooted version conflict between xampp and moodle or some configuration issue.
wondering if someone can maybe help me out a bit.
I have been working on a project that is a symfony2 web app running on Microsoft azure. it was all working great! i have my code being pulled in from git and i can easily push and update the site.
I then started working on Logins, nothing fancy, i was playing around with HTTP_BASIC athuentication and had it working after following the docs here
http://symfony.com/doc/current/book/security.html
I had a few users and i was pretty happy as id never done this before, my aim down the line is to use doctrine and databases etc but for the moment this will do.
so i had it working locally then i pushed to my branch. and boom 500 error. now i'm not sure what I've done and I've already done a bit of research, but nothing has really helped?
I read somewhere that by removing all the .htaccess files would be a fix, but no avail. the error that i'm getting is just a google 500 error and not a symfony error which makes me that I've really messed it up!
i could roll back to a previously working commit but id lose a lot of work on the front end side, but its confusing how everything is working absolutely fine locally but not on the server... please ask me any questions that could help you help me i guess!
help would be great. also, im a junior!
I built an clear symfony application, configured the security system with HTTP_BASIC authentication on local, and deployed to Azure Web app via GIT. I didn’t have 500 internal error.
So I suspect that there are some errors in the application.
Usually, when we deploy symfony applications to Azure via GIT, there several files and folders will not be updated with the application which may cause the application lack of dependent packages, we can check the list in .gitignore file in root directory.
Login on KUDU console site of your Azure Web App, the URL should be: https://<your _site_name>.scm.azurewebsites.net/DebugConsole, run the following commands in cmdlet:
cd site\wwwroot
(if you do not have composer.phar file in your project)
curl -sS https://getcomposer.org/installer | php
php composer.phar install
It will install the dependences and clear the cache.
Furthermore, we can check whether the application can run in dev mode, visit URL: http://<your _site_name>.azurewebsites.net/web/app_dev.php, if it works fine in dev mode, but rise an error 500 in prod mode known as “app.php”, we should manually clear the production cache:
Login on KUDU console site, and run php app/console cache:clear --env=prod.
If you get a [Symfony\Component\Filesystem\Exception\IOException] exception, you can manually delete app\cache\prod folder and run the command again.
Also, we can check the detail error messages in dev.log and prod.log in app\logs folder.
Beside doing file operations in KUDU console site, we can use WebMatrix on Windows to remote our sites on Azure.
So I've recently developed a CMS with Laravel and its all working great - on my local machine that is...
When I upload it to my webserver I start getting file not found errors from what I believe is composer's autoloader.
The errors originate from the require $file on line 52 (I think, I'm not at the computer right now) in the vendor/composer/autoload_real.php.
I'm not familiar with composer at all so I'm not really sure where to start. All I do know is that it works fine on my localhost but doesn't work on my server with the exact same files. I am just lost as to what to try. Any ideas?
Thanks to everyone for their support. I've got it working now.
I deleted the vendor directory, installed composer on the server, updated my files to the ones provided at laravels github, ran composer install and finally re-uploaded my config, controllers and views.
This was necessary as composer update was giving me even more errors. Either way, I've finally got it working and you guys helped a lot.
I was using Magento 1.4.1 and upgrade gracefully to 1.4.2. After testing if the upgrade was Ok, I made some modification in order to have a new home page layout for a store using these instruction. The modifications have been tested on a local version (Ubuntu 10.04, php 5.3.2), and worked great.
When I upload the files to the pre-prod server (Centos 5.5, php 5.2.14), and access the System->Configuration->design tab in the admin backend, my browser seems to keep loading indefinitly.
What I have done:
I copied the app/code/core/Mage/Page/* directory to the app/code/local/Mage/Page/;
I created the app/etc/modules/Mage_Page.xml, and defined the codePool to local;
What I have already checked:
I got no errors in /var/log/httpd/*.log;
I got no errors in magento's var/log/system.log;
The frontend works fine;
The backend can be accessed, except the System->Configuration->design tab;
I tried to revert my modifications to a revision before the modification were made (using svn);
I cleaned up the cache using rm -fr var/cache/mage* var/session/* directly on the server;
I restarted the server multiple time;
I even tried to get a dump of the db in production on the preprod server, with no effect. I still got the same issue.
If someone could point out anything I could have forgot.
I am ready to try anything to make it work, since it would not affect the production server for now.
After a lot of searching, we finally tried to reboot the apache server (we had to force it to reboot, I don't know why?). When we retried, everything was working as expected.
There probably was a corruption on the server that made crash only this tag.
Hope this could help someone.