Css changes reflect only after deploy command in magento2 - magento2

Now i have created custom theme in magento2.Every time i wrote css it doesn't reflect immediately.I have changed mode to "developer".And also disable cache
in backend.I have given the following commands to reflect my custom css.
rm -f var/* -R
rm -f pub/static -R
php bin/magento setup:static-content:deploy
chmod 0777 var -R
chmod 0777 pub/static -R
It takes too much time to do my design work.So please anyone help on this.

The solution suggested by Emizen Tech works fine and helps me out to resolve the same issue in my site.
However, it only requires mode to be set to the developer.
In order to change the mode, here is the command:
bin/magento deploy:mode:set developer

you can just write css/js for theme in the app/design same folder
to reflect the changes just remove that deployed file in pub/static folder
Magento2 will auto create the missing/deleted static files
Make sure that pub/static/.htaccess should be there for auto generation of Static Files.
as I can See you have removed the all files and folder into pub/staic folder
copy this .htaccess file form Magento's GIT Repo. : https://github.com/magento/magento2/blob/develop/pub/static/.htaccess

Easy way to directly change in pub/static folder and then it complete put this change in app/design folder that make it faster.

Related

How to recover frontend and backend css after deploy command

I have done below steps but after this frontend and backend css fonts will not working properly in magento2.
Remove pub/static //not .htaccess
Remove var/cache
Remove var/composer_home
Remove var/generation
Remove var/page_cache
Remove var/view_preprocessed
Then open up app/etc/di.xml find the path
Magento\Framework\App\View\Asset\MaterializationStrategy\Symlink
and replace it with Magento\Framework\App\View\Asset\MaterializationStrategy\Copy
And finally run this:
php bin/magento setup:static-content:deploy
I have been facing strange issue, as the part moving modifications in static content. we removed pub/static and deployed setup:static-content:deploy.
After doing this, files are generated properly in pub/static folder but when i load front end, styles are vanished.
As in the source the file paths are loading with version1483082446
root/static/version1483082446/frontend/Smartwave/porto/en_US/mage/calendar.css
I have followed below commands, but my styles are not loading in frontend.
Delete var/cache var/page_cache generated var/view_proceesed pub/static/frontend pub/static/adminhtml
Perform setup:upgrade di:compile content:deploy cache:flush
Give 777 permission to the pub var and generated folder.

Powermail: captcha always the same

i use Powermail 3.12.10 in TYPO3 7.6.16. My problem is, that the implemented Captcha alsways is the same. It does not change when i reload and across browsers.
Any ideas?
That happens if the typo3temp folder is not writeable from TYPO3. So the image can't be overwritten. Check your install tool.
Same question was asked in Slack Channel ext-powermail some days ago.
Most likely the page is cached. Make sure the plugin is included as USER_INT.
In our case it was not the file permissions, but the file owner. I set it to www-data:www-data, et voila!
To set the owner for the whole directory and subdirectories: chown -R www-data:www-data <typo3-directory>
Also, in our (older) version of TYPO3, the captcha file was not in the typo3temp directory, but in the according ext directory for powermail.

How to solve undefined labels in suiteCRM

I am getting this error in SuiteCRM:
"NetworkError: 404 Not Found -
/cache/jsLanguage/Home/en_us.js?v=9W_DRN8pphMvoAsvU564UA"
Please help me that how can I solve it?
Go to Admin > Repair and do a "Quick Repair & Rebuild".
Execute any changes shown at the bottom of the page.
If that doesn't work, go to Admin > Repair and do "Rebuild .htaccess file"
and afterward, Admin > Repair and do a "Quick Repair & Rebuild" again.
Simply remove the cache folder from your instance files, and make a hard reload.
Here are the commands you need to execute in the directory to fix this issue.
find -type d -exec chmod 755 {} \;
find -type f -exec chmod 644 {} \;
These 3 directories in SuiteCRM should be 777. or at least 775.
Cache
upload
custom
As lot of files re-generate while repair or cache build up, it needs to be full permission on those directories.
the issue for me was super simple and none of these: my .htaccess file had an old directory listed so I did a control F, changed the directory name of where suitecrm should have been and currently is, and then saved it, and boom. all 'undefined' errors gone. Hope this helps
This is related to RewriteBase in .htaccess. Either you can manually update it by modifying .htaccess or execute Rebuild .htaccess file
I had this same problem and the above answer did not work.
I found that the file/folder permissions were wrong, once these were updated 644/755 respectively everything started to work as it should.

moodle plugin installing issue?

I am unable to install the following question types with my moodle
1. Drag and drop into text (qtype_ddwtos)
2. Drag and drop matching (qtype_ddmatch)
I am using I am using Moodle 2.5.4 (Build: 20140113), php 5.4.7, MySQL 5.5.27, Apache 2.4.3, XAMPP server version 1.8.1
I have downloaded the plugins and unzip it then placed in the moodle->question->type. After that if I click the notifications link it is showing only blank page. Please advise me how to go further and how to resolve this issue and make use of those plugins.
the idea is to give the 755 permission to the "ddmatch" and "ddwtos" folders.
1- copy the two folder to moodle->question->type (as you did)
2- cd to this this directory:
cd /opt/lampp/htdocs/moodle/question/type
3- and change the permission of the two folder:
sudo chmod -R 755 ddwtos ddmatch
it worked for me !
I just checked out 2.5.4 and downloaded the plugins you mentioned - making sure they were both 2.5 versions - and extracted them into /question/type
https://moodle.org/plugins/view.php?plugin=qtype_ddmatch
https://moodle.org/plugins/view.php?plugin=qtype_ddwtos
Then went to notifications, they both require other plugins
qtype_match doesn't exist unfortunately
https://moodle.org/plugins/view.php?plugin=qtype_match
However gapselect does, so I downloaded that one too
https://moodle.org/plugins/view.php?plugin=qtype_gapselect
Then ran the upgrade and no errors were shown.
Is this on linux? Its possible that the extracted files haven't got the correct permissions - check the ownership of the folders : http://docs.moodle.org/25/en/Security_recommendations#Running_Moodle_on_a_dedicated_server
I would also double check that the files have been unzipped into the correct folder - so you should have /question/type/ddmatch, /question/type/ddwtos and /question/type/gapselect
If all that is okay then, like davosmith says, if you can switch on debugging and paste the error here. If you can't get into the system then edit /config.php and add these 2 lines after $CFG = new stdClass();
$CFG->debug = 32767;
$CFG->debugdisplay = 1;
Then try going to notifications again and see what the error is /admin/index.php

there has been an error processing your request magento 1.7

There has been an error processing your request magento 1.7
Exception printing is disabled by default for security reasons.
Error log record number: 1116398732
Someone has a solution for this error? Please solve my problem
report number represent specific files in var/report folder in magento root
open var/report/ in your magento root dir,
open file called same as your report number , in this case: '1116398732'
paste contents here and we will proceed with finding out what was wrong
You can check the report by going to /var/report
Usually it occurs because of uncleared cache. Just go to /var/cache and delete all the files in cache folder. Refresh the page, it should work.
There are three simple steps to resolve this issue:
1- create tmp directory in your magento site
2- go to magento site/errors directory and update local.xml.sample to local.xml
3- go to magento site/lib/Zend/Cache/Backend/File.php and replace 'cache_dir' => null, to 'cache_dir' => 'tmp',
NOTE:tmp directory permission should be #777
Delete the generated/code directory rm -rf generated/code
Then run
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento cache:flush
chmo -R 0777 var/ pub/ generated/
Now try to run the site, it should be perfect now. Cheers