Create drupal 9 platform in Aegir - drupal

Need to create a new platform for Drupal 9 in Aegir.
I have created a makefiles in the path /var/aegir/platform/makefiles/d9.make
api = 2
core = 9.x
projects[] = "drupal"
While adding the new platform by using the make file in the Aegir site, it has an error "No release history available for drupal 9.x."
Seems we have release for https://updates.drupal.org/release-history/drupal/8.x
But not for https://updates.drupal.org/release-history/drupal/9.x

Related

Symfony console output creates extra unwanted characters

i got this weird error, where every output in the console with symfony creates some extra characters. The following is the output after a basic symfony in the console.
$ symfony
←[32mSymfony CLI←[39m version ←[33mv4.22.0←[39m (c) 2017-2021 Symfony SAS
Symfony CLI helps developers manage projects, from local code to remote infrastructure
These are common commands used in various situations:
←[33mWork on a project locally←[39m
←[32mnew←[39m Create a new Symfony project
←[32mserve←[39m Run a local web server
←[32mserver:stop←[39m Stop the local web server
←[32msecurity:check←[39m Check security issues in project dependencies
←[32mcomposer←[39m Runs Composer without memory limit
←[32mconsole←[39m Runs the Symfony Console (bin/console) for current project
←[32mphp, pecl, pear, php-fpm, php-cgi, php-config, phpdbg, phpize←[39m Runs the named binary using the configured PHP version
←[33mManage a project on Cloud←[39m
←[32mlogin←[39m Log in with your SymfonyConnect account
←[32minit←[39m Initialize a new project using templates
←[32mlink←[39m Link current git repository to a SymfonyCloud project
←[32mprojects←[39m List active projects
←[32menvs←[39m List environments
←[32menv:create←[39m Create an environment
←[32mtunnel:open←[39m Open SSH tunnels to the app's services
←[32mssh←[39m Open an SSH connection to the app container
←[32mdeploy←[39m Deploy an environment
←[32mdomains←[39m List domains
←[32mvars←[39m List variables
←[32muser:add←[39m Add a user to the project
Show all commands with ←[32msymfony.exe help←[39m,
Get help for a specific command with ←[32msymfony.exe help COMMAND←[39m.
As you can see, I get this ←[33m here and there. Any help is gratefully accepted. Please let me know if you need any additional information from me.
$ bin/console --version
Symfony 5.2.1 (env: dev, debug: true)

Drupal ComputedItemListTrait::getValue() must be compatible FieldItemList::getValue($include_computed = false)

Hey so my hosting provider dropped support for anything below php 7 so need to update my drupal site from 8.4 to 8.6 so i wont break etc.
when trying to update running the 'composer outdated "drupal/*"' command nothing is returned at all even when I added '"drupal/core": "^8.6.1"' to the 'require' section of the 'composer.json'
and the site is mostly fine but i cant add any content and get the following error :
Fatal error: Declaration of Drupal\Core\TypedData\ComputedItemListTrait::getValue() must be compatible with Drupal\Core\Field\FieldItemList::getValue($include_computed = false) in \core\modules\path\src\Plugin\Field\FieldType\PathFieldItemList.php on line 13
and here is some of my composer.json which mentions drupal
"require": {
"composer/installers": "^1.0.24",
"wikimedia/composer-merge-plugin": "^1.4",
"drupal/core": "^8.6.1"
},
"replace": {
"drupal/core": "^8.4"
},
so i'm summary im not even sure my drupal has been updated but the site works fine apart from where I add content I get a php error saying a module is not compatible for the core.
That error looks like a PHP 7 compatibility issue, so I would assume that your Drupal version has not been updated.
You can check your current version of Drupal on the status report page when logged-in - Reports > Status report (from the administrative toolbar) or https://yoursite.com/admin/reports/status
Running composer require directly (rather than editing composer.json) is the best way to ensure an appropriate version of Drupal core is correctly installed, as follows:
$ composer require drupal/core^8.6.1
This will ensure the composer.lock file is also updated when installing an appropriate version of Drupal core.

Instalation of Intershop 7.9 failing on missing version for demo cartridges

I'm trying to install a demo shop of Intershop version 7.9 but i'm failing to get it working. When I run "gradlew deployServer" I'm getting an error on all dependencies of the first demo shop cartridge:
Could not resolve all dependencies for configuration ':app_sf_responsive:compile'.
Could not resolve com.intershop.business:ac_ecircle:.
Required by:
nl.test.testproject:app_sf_responsive:1.0.0-LOCAL
No version for module 'com.intershop.business:ac_ecircle' in project properties and no version declared in dependency. Consider adding a version or filter property to 'C:\projects\test7.9\projects\testproject\gradle.properties'
I have followed the complete Intershop manual Setup CI Infrastructure but there is one point I don't know exactly what to do, that's with the new versioning plugin.
It is in chapter 6.2.5, any one have an idea how to configure that?
After loads of tinkering and mails back and forth with Intershop support I found a solution.
My alterations are in section 7.2.4 of the Setup CI Infrastructure of Intershop:
https://support.intershop.com/kb/index.php/Display/279D85#Cookbook-SetupCIInfrastructure-CorporateArtifactsRecipe:SetupCIBuildforCorporateArtifacts
I Made sure the corporate distribution is unique since I have more that 1 Intershop installation. Otherwise the upload to Nexus(in my case) will still fail.
In the build.gradle of the corporate distibution folder added disableSCM = true in the scm.version section. It now looks like this:
scm {
version {
type = 'threeDigits'
increment = 'MAJOR'
patternDigits = 1
disableSCM = true
initialVersion = '2.0.0'
}
}
If this is not added I got a bad request httpstatus 400 from Nexus because it tried to upload it as a snapshot while the distribution repository is a release repository.
Another problem is the distributionURL in the project/gradle/wrapper/gradle-wrapper.properties
All Nexus repository URL's are build up with < repoBaseURL > + repositories/snapshots, but the distributionURL is missing the repositories part.
After applied those changes it worked for me.

How to download a specific version of ASP.NET MVC 5 source code

I'm looking for ASP.NET MVC 5.0 RTM source code. I've tried to download this from http://aspnetwebstack.codeplex.com/ but it seems to have only the most recent version 5.1.1 RTM. I've tried with no success to download for a specific tag or branch. In Source Code tab, in field "Browsing Changes in" the only options are "master" or "v3-rtm".
Could someone help me with this?
As per their wiki:
MVC 5.2.3 RTM = v3.2.3 (commit 0e974218e12a)
https://aspnetwebstack.codeplex.com/SourceControl/changeset/view/0e974218e12a
MVC 5.2.2 RTM = v3.2.2 (commit 66298100f4e3)
https://aspnetwebstack.codeplex.com/SourceControl/changeset/view/66298100f4e3
MVC 5.1.3 RTM = v3.1.3 (commit 0150245a9e34)
https://aspnetwebstack.codeplex.com/SourceControl/changeset/view/0150245a9e34
MVC 5.1.1 RTM = v3.1.1 (commit 54866f0d3262)
https://aspnetwebstack.codeplex.com/SourceControl/changeset/view/54866f0d3262
MVC 5.0 RTM = v3.0 (commit 39391d3a64d7)
https://aspnetwebstack.codeplex.com/SourceControl/changeset/view/39391d3a64d7
MVC 4.0 RTM = v2.0 (commit 89b9166ca722)
https://aspnetwebstack.codeplex.com/SourceControl/changeset/view/89b9166ca722
In general way, if you have already cloned the repository. You can use the Git commands:
git show-ref --tags
Your will see something like:
89b9166ca72279fcb62bff67c6224993371ed765 refs/tags/v2.0
a1b7c04f72277e6dfc459d8d6948260d26ccc6c9 refs/tags/v2.0-rc
d4dab6e6c0b181ee56593a3a514faab7f407e1f2 refs/tags/v2.0.1
f276aa28c436c598e3c2a8e09d052e2b17630ab0 refs/tags/v2.0.2
75b5e7ea58d2a120242ff0d840600e33e9b65882 refs/tags/v2.0.3
26665357e13c050d298310e0f5c7925af32a66cd refs/tags/v2.0.4
1b78397f32fc13ea321647b5039755df4be58558 refs/tags/v2.1
235544cf12a25d2fd072c1eafec4c681c9d6068e refs/tags/v2.1-beta
f079d76e57b557d0215dbbaf5d398f64a74ebf90 refs/tags/v2.1-rc
39391d3a64d71ae735f7620ae082aea5f05cb0e0 refs/tags/v3.0
...
or
git tag -n
And all tags with their comments will be promped:
fbv1.0 Microsoft.AspNet.Facebook v1.0
fbv1.1 Upgrade ODataLib version from 6.7.0 to 6.8.0
fbv1.1-beta Microsoft.AspNet.Facebook 1.1.0 Beta
odata-v5.3 Update Microsoft.AspNet.Facebook version.
v2.0 Added copyright statements to files lacking it.
...
Select the version to download by the tag, and executed the git rev-parse command to get the id of the commit: For example:
> git rev-parse --short=12 v3.2.3
> 0e974218e12a //This is the first 12 characters of SHA commit.
With the first 12 characters of the SHA of the commit you can now build the url. For example:
Version 3.2.2 = https://aspnetwebstack.codeplex.com/SourceControl/changeset/view/66298100f4e3
Version 3.2.3 = https://aspnetwebstack.codeplex.com/SourceControl/changeset/view/0e974218e12a
...
or just call git checkout command:
git checkout v3.2.3
This might be helpful when looking for sources of concrete MVC/WebAPI/Web Pages version:
https://aspnetwebstack.codeplex.com/wikipage?title=Building%20from%20Source
Looks like the CodePlex repo, with all history, was migrated to GitHub!
https://github.com/aspnet/AspNetWebStack
They even have a milestone for ASP.Net MVC 5.2.4, although it seems somewhat dead:
https://github.com/aspnet/AspNetWebStack/milestone/1
The Releases tab contains the appropriate versions as per #outlookrperson's answer (basically, add 2 to the major version in the tag, e.g. tag 3.2.3 = MVC 5.2.3).

Drupal app development

name = MagApp 1.0
description = Magapp module that enables MagApp powered publications.
core = 7.x
php = 5.1
package = MagApp
dependencies[] = references
dependencies[] = node_reference
dependencies[] = magapp_core_content_types
version = "7.x-2.0"
I have been created a module and the info file is written above is there any problem while changing the php version , Because i did it before months , so i have to update this module , Can i add dependencies directly without using modules .
Search the source of /modules for admin/structure and check how they built that *_menu() hook.
If you have access to the server and it's running *NIX you could do:
grep -ri 'admin/structure' your_site_directory/modules/*
And then you can implement your own hook_menu() in your own module. Might also be possible in the Structure -> Menu system of the web UI. I don't recall.

Resources