# Htacess persist settings after upgrade

**URL:** <https://forum.mautic.org/t/htacess-persist-settings-after-upgrade/19305>\
**Category:** Product Support\
**Created:** [May 3, 2021, 1:41am UTC](https://forum.mautic.org/t/htacess-persist-settings-after-upgrade/19305 "2021-05-03T01:41:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tornmarketing](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/tornmarketing/32/11603_2.png) [@tornmarketing](https://forum.mautic.org/u/tornmarketing)\
**Post date:** [May 3, 2021, 1:41am UTC](https://forum.mautic.org/t/htacess-persist-settings-after-upgrade/19305/1 "2021-05-03T01:41:48Z")

</div>

**Your software**  
My Mautic version is: v3.3.3  
My PHP version is: 7.4  
My Database type and version is: mysql

**Your problem**  
My problem is:  
After each upgrade the htacess file get completely replace, whipping out any settings we have in the system for whitelisting any custom files.

We have a CRON commands PHP file we use to run alot of various functions

> **[virgilwashere/mautic-cron-commands](https://github.com/virgilwashere/mautic-cron-commands)**
>
> Script to run Mautic commands from a web page. Contribute to virgilwashere/mautic-cron-commands development by creating an account on GitHub.

after each upgrade we have to go into the htaccess file and then add |commands to the whitelist otherwise it throws a 403 error. This is the same if we configure anything from the servers control panel it also throws a 403.

All other platforms we run we are able to run an upgrade that respects any other configured logic in the htaccess rather than replacing the file completely.

For instance in WP there is logic to replace the basic line logic between 2 set parameters  
with each plugin handling their own logic between their own parameter start/finish handles