Upgrading Version

Upgrading from 4.6.0 to 4.7.0

Modify your config/config.php to use the new config file for Security_headers class. Replace your old error pages in app/views/errors/ with the new ones in app/views/errors. Replace your old welcome_page in app/views/ with the new one in app/views/. Remove $config[‘allowed_origins’] from config/api.php. It is now configurable in config/config.php. Replace all files and directories in your scheme/ directory.

Note

Before performing an update, you should take your site offline by replacing the index.php file with a static one.

Upgrading from 4.5.0 to 4.6.0

Update your index.php ROOT_DIR from __DIR___ to dirname(__DIR__) and put it to your public directory. Update the .htaccess in your root to this:

RewriteCond %{REQUEST_URI} !^/public/
RewriteRule ^(.*)$ public/$1 [L,QSA]

Add .htaccess file inside public directory and put this:

<IfModule mod_rewrite.c>
   <IfModule mod_negotiation.c>
      Options -MultiViews -Indexes
   </IfModule>

   RewriteEngine On

   # Handle Authorization Header
   RewriteCond %{HTTP:Authorization} .
   RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

   # Redirect Trailing Slashes If Not A Folder...
   RewriteCond %{REQUEST_FILENAME} !-d
   RewriteCond %{REQUEST_URI} (.+)/$
   RewriteRule ^ %1 [L,R=301]

   # Handle Front Controller...
   RewriteCond %{REQUEST_FILENAME} !-d
   RewriteCond %{REQUEST_FILENAME} !-f
   RewriteRule ^(.*)$ index.php/$1 [L]
</IfModule>

# Optional: Deny access to sensitive files
<FilesMatch "^\.env|composer\.json|composer\.lock">
   Order allow,deny
   Deny from all
</FilesMatch>

Upgrading from 4.4.1 to 4.5.0

Replace all files and directories in your scheme/ directory.

Note

Before performing an update, you should take your site offline by replacing the index.php file with a static one.

Upgrading from 4.4.0 to 4.4.1

Replace all files and directories in your scheme/ directory.

Note

Before performing an update, you should take your site offline by replacing the index.php file with a static one.

Upgrading from 4.3.1 to 4.4.0

Add the new configuration file ember.php to your app/config/ directory. Replace all files and directories in your scheme/ directory.

Note

Before performing an update, you should take your site offline by replacing the index.php file with a static one.

Upgrading from 4.3.0 to 4.3.1

Replace all files and directories in your scheme/ directory.

Note

Before performing an update, you should take your site offline by replacing the index.php file with a static one.

Upgrading from 4.2.* to >=4.3.0

Replace all files and directories in your scheme/ directory.

Note

Before performing an update, you should take your site offline by replacing the index.php file with a static one.

Upgrading from 4.* to >=4.2.5

Replace all files and directories in your scheme/ directory.

Note

There are some changes in the config.php file. Please back up your old version, then replace it with the new one. After replacing, update it based on your current configuration.

Note

Before performing an update, you should take your site offline by replacing the index.php file with a static one.

Upgrading from 3.* to >=4.0

Replace all files and directories in your scheme/ directory.

Note

There are some changes in the config.php file. Please back up your old version, then replace it with the new one. After replacing, update it based on your current configuration.

Note

Routing in LavaLust 4 is very different compared to LavaLust 3 and below. It is now similar to the modern routing of other full-stack frameworks.

Before performing an update, you should take your site offline by replacing the index.php file with a static one.