Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
V
varbase-3293696
Manage
Activity
Members
Labels
Plan
Custom issue tracker
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Model registry
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Issue forks
varbase-3293696
Commits
18400039
Commit
18400039
authored
7 years ago
by
Rajab Natshah
Browse files
Options
Downloads
Patches
Plain Diff
Updated CHANGELOG.md, UPDATE.md, and README.md
parent
02c4fbb2
No related branches found
No related tags found
No related merge requests found
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
CHANGELOG.md
+45
-0
45 additions, 0 deletions
CHANGELOG.md
README.md
+1
-1
1 addition, 1 deletion
README.md
UPDATE.md
+47
-0
47 additions, 0 deletions
UPDATE.md
with
93 additions
and
1 deletion
CHANGELOG.md
+
45
−
0
View file @
18400039
## 8.4.03
Issue #2868568: Updated [Bootstrap] theme from 8.3.2 to 8.3.3
Issue #2865977: Establishing profile inheritance for new distros
Issue #2869287: Disabled [imagemagick] module on install, as some basic servers
do not have needed functions for imagemagick to work.
Issue #2869329: Optimized varbase installation Config and ConfigBit engine, for
sub profiles integrations
Issue #2865977: Change the location of libraries from Varbase profile folder to
the Drupal root of th project.
Issue #2865977: Have libraries in the list of enabled modules in order after
installing Drupal core, and Varbase core and default features
installation step.
Issue #2870032: Updated [Redirect] module from 8.1.0-alpha4 to 8.1.0-alpha5
Issue #2870025: Changed Layouts of [Default, and Full Content] view modes to
use [Bootstrap layouts] for Landing page, and Basic Pages.
Issue #2870172: Added [ Feature: Website Base Requirements - Website Languages
-
English ] for Automated Functional Testing
Issue #2870172: Added [ Feature: Content Editing - Rich Text Editor - Easy
linking to internal content by searching for content by its
titles ] for Automated Functional Testing.
Issue #2870172: Added [ Feature: Content Editing - Rich Text Editor - Input
formats ] for Automated Functional Testing.
Issue #2870172: Added [ Feature: Content Structure Features - Basic Pages
-
Basic page ] for Automated Functional Testing.
Issue #2870172: Added [ Feature: Content Structure Features - Basic Pages
-
Pages with pre-defined layouts] for Automated Functional
Testing.
Issue #2870172: Added [ Feature: Content Editing - Rich Text Editor - Easy
linking to internal content by searching for content by its
titles ] for Automated Functional Testing
Issue #2870617: Removed 2845037_15.patch for the [Entity Browser] module
Issue #2870172: Updated Behat Step definitions for [Editor Media Browser] and
to click, or double click on an image with the provided
title/alt text.
Issue #2870172: Added [ Feature: File & Media Management - Assets Management
-
Ability to embed existing media image library in the rich
text editor ] for Automated Functional Testing.
Issue #2870969: Updated [ctools] module from 8.3.x-dev to 8.3.0-beta2
Issue #2870974: Updated [panels] from 8.4.x-dev to 8.4.0-beta1
Issue #2870977: Updated [Page Manager] from 8.4.x-dev to 8.4.0-beta1
Issue #2870980: Updated [Panelizer] from 8.4.0-beta2 to 8.4.0-beta3
Issue #2870985: Removed 2868095-2.patch for the [bootstrap layouts] module:
as the patch were committed.
Issue #2871201: Updated [Drupal core] from 8.3.0 to 8.3.1
## 8.4.02
*
Issue #2864089: Updated [Crop API] module from 8.1.0 to 8.1.1
*
Issue #2864090: Updated [Slick Carousel] module from 8.1.0-rc2 to 8.1.0-rc3
...
...
This diff is collapsed.
Click to expand it.
README.md
+
1
−
1
View file @
18400039
...
...
@@ -26,7 +26,7 @@ instructions.
## Install with Composer
```
composer create-project Vardot/varbase-build:^8.4.0
2
PROJECT_DIR_NAME --no-dev --no-interaction
composer create-project Vardot/varbase-build:^8.4.0
3
PROJECT_DIR_NAME --no-dev --no-interaction
```
## Building Varbase 8.x-4.x projects with Varbase Build
...
...
This diff is collapsed.
Click to expand it.
UPDATE.md
+
47
−
0
View file @
18400039
...
...
@@ -76,6 +76,53 @@ while working on the project.
*
Done :
\)
---
# Varbase 8.4.02 to Varbase 8.4.03
If you are updating from Varbase 8.4.01 or earlier, please follow the steps
to updated to Varbase 8.4.02 first. in the UPDATE.md file.
## Updating files with Copy and Paste for Varbase 8.4.02 to Varbase 8.4.03
```
Given that we are at the drupal root folder for varbase
When we delete all drupal core folders and files
And we copy all new Varbase files drupal root folder for varbase
And we make sure that we have all custom module or themes still in the "sites" folder
And we make sure that all new used modules and features are present.
Then we will be ready to update the active config and database.
```
## Updating files with composer from Varbase 8.4.02 to Varbase 8.4.03
```
Given that we are at the root folder for varbase project, not the docroot
And we make sure that the current "Varbase-Build" composer.json file and files are the latest
When we delete the "vendor" folder
And we delete the "composer.lock" file
And we run the "composer require vardot/varbase:8.4.03" command
And wait for composer to finish work
Then we should not see any issues in the terminal
And we should see "Writing lock file" in the terminal
And we should see "Generating autoload files" in the terminal
When the composer finishes work with no errors
Then we will be ready to update the active config and database.
```
## Updating the active config and database from Varbase 8.4.02 to Varbase 8.4.03
```
Given that we are in the docroot of the current Varbase project
And all files are updated using (copy and past) or (composer require/update
When we run drush "updb" or go to "/update.php"
Then we should see the steps of updates.
When we run drush "updb" or go to "/update.php" again
Then we will have the site update with the new Varbase 8.4.03 version
When we go to "/admin/config/development/features"
Then we should see "Changed"
When we follow with each feature to import new changes.
Then we will have the Varbase site updated to the latest version.
```
---
# Varbase 8.4.01 to Varbase 8.4.02
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment