You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to display the documentation home page for my package on its tg/tgwebvalid page, but this can't be achieved by specifying the homepage field in the composer.json file
After monitoring several other packages, I came to the conclusion that the home page is displayed only if it is specified in the master branch.
And since my current default branch is 4.x, it doesn't work. However, the rest of the fields are displayed correctly, they are pulled from the default branch. And this field, obviously not.
The text was updated successfully, but these errors were encountered:
In the package information block, there is also a link with the text Documentation, and it also refers to the master branch, and ignores that the default branch in the repository is 4.x
I can't reproduce this. Per the code the homepage is taken from the data of the default branch.. And it seems like your package is showing the correct info now.
I looked for a solution for a long time and nothing helped. However, at one point I still solved this problem.
Now, as far as I understand, the home page wasn't showing because it was added to composer.json after the package was published to packagist
Accordingly, in order for the data to become available, I had to click the "Edit" button in the package control panel and click the "Update" button that appears after that. That is, a kind of updating the link to the repository so that it is read again
Hello
I'm trying to display the documentation home page for my package on its tg/tgwebvalid page, but this can't be achieved by specifying the homepage field in the composer.json file
After monitoring several other packages, I came to the conclusion that the home page is displayed only if it is specified in the master branch.
And since my current default branch is
4.x
, it doesn't work. However, the rest of the fields are displayed correctly, they are pulled from the default branch. And this field, obviously not.The text was updated successfully, but these errors were encountered: