Laravel + PhpStorm caching issue - laravel

I have downloaded my project from the server to local exclude tests, storage and .cache directories.
When i going to change some blade files -> save+upload. I see no changes on my website.
I can see them after artisan view:clear command.
However, then I'm using FileZilla with notepad++ or even phpStorm remoteHost mode. I can see every changes at once on my website.
Can someone explain me this moment? How it's possible to fix it?

I solved my problem by removing option Preserve files timestamps.
I spent a huge amount of time on this! Hope it helps someone

Related

Server Caching?

So, i have this issue where I've uploaded a web page and some supporting files (css, images, etc) - but when I make changes and upload the files, the changes don't show up.
I've tried clearing my local cache, deleting and re-uploading files, and even went into the server's cpanel (I have access to the WHM and backend) to do it directly through the file manager. No changes are taking effect.
I went through and checked the source code to the css file and it's not the same as what I'm uploading.
Is there something I'm missing? Is there such a thing as caching on the server? If so, how do I empty the cache, or fix the issue?
I'm kind of desperate.
Thoughts?
OK! As it stands - I have solved the problem.
The issue was SiteLock Security. It caches a great deal of information that we don't want. While on the phone with support, they ended up showing me how to get 1) purge the caching, and 2) change the settings for caching specific information.
I DO want to thank you all for your input. I DID lead me down the right path. Kudos to you!
Thanks, again!
-mb

Strange forward slash in 'clean' Laravel project

I was developing as usual on my Laravel project tweaking with the Queue driver settings in my .env file, when all of a sudden a random forward slash appeared at the top of my project which caused some random issues. I've cleared all cache's, routes, views etc but I am still getting the strange forward slash. I even get it in the console when I run a command.
Every page:
I assume its some kind of strange bug in Laravel. Hopefully someone can tell me whats the issue. Thanks in advance.
check you files in the config folder: app.php, database.php, ... and also public/index.php and look for a \ before the <?php or if you closed it somewhere.
if you find nothing, lookout for an echo in those files. (on windows use grepwin for fast search)

VScode: how to setup for local edit and ftp-deplyment

I used to use Dreamweaver. I've a huge Classic ASP website. I edit the files on my local system, and when done, I can upload the file(s) via ftp to the remote webserver. Now, I try to switch to VSCode. I've installed ftp-simple, ftp-sync and deploy. But can't find the set-up to get a Dreamweaver like behaviour. Eg, I have to locate for each file I want to upload/deploy, the exact location in the remote file tree.
I really feel like deploy deserves more attention. I spent the past 4 days or so to find an extension that does just that. Auto-upload to an ftp-folder from a local folder. I wanted to make git work for my website, but couldn't get that to work on the server with ftp-simple or ftp-sync because those extensions only download the opened files or open in a different temporary folder each time. I set up deploy now and got exactly what I wanted thanks to your tiny comment, thank you!
(I'm sorry if this post is too old to comment on, but I browsed Stack overflow for days to find this, so I thought it might help others in the future to point this out.)
it sounds like your just missing your mapping configuration. Most text editor FTP packages include a configuration file where you specify the server, your credentials, and the root folder of your ftp server. Have you specified this?

Removing default migrations from Laravel

After creating a new Laravel project with laravel new, there are a couple of migration files in the database > migrations folder:
2014_10_12_000000_create_users_table.php
2014_10_12_100000_create_password_resets_table.php
These seem to be examples of typically useful migrations and are probably a good place to start if you need a system that requires something similar. However I'd like to delete them so they don't clash with something in a new project I'm building.
I was hoping I would be just able to delete the files, as I've not run php artisan migrate yet, but when I try my IDE says:
Why are these files already tied into the system, and how can I safely remove them? Is there some documentation on the Laravel site that I've not been able to find about this?
I guess I could ignore the warning and try running composer dump-autoload -o, but is this really OK?
Why are these files already tied into the system
to map all project classes
how can I safely remove them?
Ignore IDE and delete them then run composer dump-autoload and will remap project classes
Is there some documentation on the Laravel site that I've not been
able to find about this?
i don't see any thing about this in laravel documentation site
Ignore the warnings and delete them. The migrations that come out of the box are to help you get started with basic auth. You don't necessarily need them. Run composer dump-autoload when you're done.

Error after transfering Laravel files to production

I just moved my project to new server and after that I'm getting this message:
Whoops, looks like something went wrong.
I've changed permissions to "storage" folder and sub-folders... to 777 and nothing changed...
I wanted to see the logs... but even with 777 permissions there is no log file... :/
I also tried to get more details from the error by setting debug mode to true... but it changes nothing... :/
What needs to be done after moving files to server? Do i need to change some config to make it work?
I did the same with clean installation of Laravel 4.2 and i got the same problem... :/
UPDATE:
Actions made after installing new laravel 4.2 instance:
check i its working ("You have arrived.") so it's working.
create "app/config/production/app.php" (with debug => true)
transfer all files through ftp
change permissions to 777 for storage dir
check if its working: ("Whoops, looks like something went wrong.") its not... :/
page is here...
http://dev.slashlab.pl/lara-test/public/
(if this can help with anything... :/)
I hope this doesn't sounds too bananas -- but are you sure you're uploading and working in the right folder? If you've both changed the permissions on your files, and edited the debug configuration in all your app.php files to no effect, one possibility is you're editing the wrong files.
There are (mostly) 2/3 places, where your configuration could be. app/config/app.php , app/config/local/app.php and app/config/production/app.php. If you set debug to true in this 2/3 places and then upload them, it is not possible to have this error page. After upload, try to download it to your computer and check the file (is it correct).
So... after a long struggle... I found a solution... ;)
The problem was that on remote host i had magic_quotes_gpc turned on
Everything started to work flawlessly after turning it off. (same for laravel 4.2 and 5.0).
Thanks to all that helped, because every little answer pushed me few steps forward. :)

Resources