It's me again,
I just found out that Reload module became active and there is no way to turn it off. Its nowhere in module lists and so on. Is this some kind of new implementation, because it's not fair to enforce me using a module which I don't want to use.
Also I'm on 2nd type paid account and it costs me dearly for the services I get.
Please respond because I'm loosing precious time because of your fault.
Regards,
Ivan Popjelev
you can disable Reload by unchecking the core.general.reload checkbox in the App config section in your Toolkit.
Or, you can edit the config.json file to set reload: false if you prefer.
If you've migrated an app across from v1.4 to v2.0.0, we respect the Reload setting in the original app: we don't automatically enable Reload during the migration or anything like that.
Related
I have a running Kentico 11 portal engine site and need to update the transformations in my navigation menu control. Something I have done many times before.
Today I went through all of the steps and the save button does not update the code. It never displays the change were saved messaging.
When I open the browser dev tools I see several errors on the page:
errors
A couple of things to check.
Is this happening in different browsers, also?
Can you save other transformations?
On this particular web part, if you select a different transformation, will that save successfully?
And, is the event log registering any errors?
Sounds like it may be a caching issue. What I'd suggest is the following:
restarting IIS
Open a private browser window and log in
attempt to make an edit to the code in question
If this does not resolve the issue, have you made any changes recently to the web.config, in particular the CMSHashstringsalt value? If so, this will cause your macros to become invalidated. You'll need to go to System > Macros > Signatures and check both boxes and resign the macros. It may take some time depending on your site but this could also help resolve your issue.
My PingFed has a connection to a SSO page. That page doesn't have the verbiage I want even though I changed and replaced the properties files. How can I rebuild so that it works?
I agree with Andrew K's comment above, but my guess here is that your updated messages are not being used because you either need to restart PingFederate or disable caching of the message properties files.
For more details, see the tip at the bottom of this page (cache-language-pack-messages setting in <pf_install>/pingfederate/server/default/data/config-store/locale-options.xml): https://docs.pingidentity.com/bundle/pingfederate-101/page/ujv1564002982909.html
Is there a way we can redirect /hac/platform/init to a Hybris 404 like how it happens for /hac/platform/init/execute? Also guide me with the ant targets that I must use to see the changes that I make on init.jsp and init.js (they don't go live on fly).
I hope you want to protect the initialization trigger, which could be accidental.
Hybris OOTB you can lock the HAC system initialization.
To lock the system for initialization and update add the unlocking (system.unlocking.disabled=true) properties to your local.properties file and rebuild your system.
You can also unlock it without restarting the system.
Set system.unlocking.disabled to false (HAC>configuration)
Go to /hac/platform/init, Click on Unlock.
Refer blog for more details and other ways to block the URL itself - Answering your actual question.
Lock system initialization screen and protect it by setting system.unlocking.disabled=true
I'm in charge of a website developped with symfony. This website is in prod.
I would like to know how to reinstall the front-end console, because im completely blinded in my task.
I suspect you're talking about the "Web Debug Toolbar":
You can control the visibility of the Web Debug Toolbar in the settings.yml. Set the web_debug parameter to true for the environment you're using. After clearing the cache with symfony cc the toolbar should be visible.
But be warned: enabling the toolbar, will make this visible to all visitors! You probably don't want this!
So depending on your problem I'd first go for enabling logging in production, and analyze the logfiles. If that doesn't solve your issue, copy the frontend_dev.php file to your production server, update it's IP to match your own, and set the environment to test. Next, set the web_debug property in test to true. Clear the cache, and navigate to this scriptfile. This way you can test, while normal users can't access the debug bar.
I'm developing a site in Drupal 6, and I'm going mad trying to work out why pages (specifically pages containing views), I'm working on locally are caching content instead refreshing the contents of the page, and that of linked js files, I'm relying on for making a mashup - is there a checklist I can check against to be sure I'm not missing when trying to deactivate caching?
These are the steps I'm taking:
On the server:
set the site to rebuild the theme on each load
cleared cache using drush (as in drush #dev cc all`) on each page load
checked that the json output from a view isn't caching
disabled any css or js caching in admin/settings/performance
On Firefox/firebug
using the web developer extension, disabled the cache
been refreshing the site using shift-F5 to force a clear of the cache
I'm not using varnish or memcached, nor any other caching modules like boost - it's straight Apache-PHP through to Drupal and MySQL.
What am I missing here?
The three things you need to do are:
Go to Site Configuration -> Performance:
Set the following options, and click Save configuration:
Caching mode: Disabled
Minimum cache lifetime: none
Page compression: Disabled
Block cache: Disabled
Optimize CSS files: Disabled
Optimize JavaScript files: Disabled
Click Clear cached data.
Go to Site building -> Views -> Tools:
Check Disable views data caching and click Save configuration.
Click Clear Views' cache.
Install the Devel module, and go to Site Configuration -> Devel settings:
Check Rebuild the theme registry on every page load and click Save configuration.
This will make sure all registries and caches except for the menu router will be rebuilt on every page, effectively preventing caching in practice.
If you really need the menu router to be rebuilt on every page (it's completely unnecessary, as you only need to worry about it when you change your implementation for hook_menu() or hook_menu_alter()), you could add menu_rebuild() to hook_init() in a custom module:
function mymodule_init() {
menu_rebuild();
}
First you don't need to do drastic things like clear cache using drush #dev cc all on each page load. Also you really don't need to have the theme registry get built on every page load unless you're doing some theme development
Make sure that page caching is set to disabled at /admin/settings/performance
Make sure you don't have some funny .htaccess rules in your drupal site and your .htaccess is the default one that comes with drupal. You might want to make sure the headers for html files generated by Drupal have an expiry in the past and the html has no-cache in the header.You have already clarified you're not using boost, varnish, memcached. It might be a good idea to make sure mod_expires apache module is enabled also.
Make sure in each view under Basic Settings Caching is set to None [I suspect this might be a source of your views not updating]
Are you using windows? If so its not the best environment for apache + PHP and I'll recommend you install Ubuntu 9.10 or an earlier in VirtualBox (Recommending Ubuntu 9.10 or earlier as it has PHP 5.2. PHP 5.3 is not very well supported by Drupal). You can use the seamless mode -- its really very cool.