I have tried unsuccessfully to use the code suggested in the question from , to see if I can use tags instead of categories. This is the function from that question:. I am afraid I am not knowledgeable enough in PHP and MySQL to work out how blog categories and blog posts are related, in order to write the correct query function.
The link you are referencing is a little old now, it'll work but looks like it was used for another purpose. Correct me if I am wrong, you are look to have the blog posts available on a different page? The ability to pull blog post data from the database onto another page But that will give you all the blog posts to deal with.
It would be best to filter the results using the page below. The filtering code here is a lot newer, for example below I have included code for sorting and limiting:. Thanks helenclarko , Yes but the issue i am having is filtering the blogentry by category. If i query just a blog entry i have no way of knowing what category the entry blongs to and thus cannot filter by the category.
With CMS 4. Tagged cms 4 , CMS 4. Posted 28 January This release focuses on an improved view for Content Managers to track where files are being used in your project.
Highlights for Developers include PHP 8 support, the ability to trigger actions from the toast notification component, plus a wide range of house-keeping improvements and fixes.
Tagged silverstripe cms , Dependencies , Vulnerability checks. Posted 22 October How are you tracking security advisories in your dependencies? Silverstripe regularly publishes security fixes and there are various tools to get notified. Read all about them here. Tagged gatsby , gatsbyjs , static site generation , Javascript , first table , Headless. Posted 6 August Gatsby is a development framework that delivers high performing websites and apps.
Lead Developer at First Table , Gene Dower shares his experience with this web development dream team. Posted 21 July Posted 14 July We've stayed focused on how to keep your content within Silverstripe CMS secure to avoid any potential content leaks. Tagged Community Survey , feedback , results , SilverStripe. Posted 12 June Our annual Community Survey highlights how the community are using Silverstripe CMS and offers important insight for our product development team.
Posted in Platform , Developers , Company. Posted 24 April This was one of our most frequently requested new features, designed to automatically provision and deploy a free SSL certificate for your website. Tagged cms 4 , patch release. Posted 15 April A new security patch release has been made available for sites on CMS 4 to address issues identified with restricting access to some files saved in the CMS.
The command checks out from the 4. To check out from master instead, replace 4. The --keep-vcs flag will make sure you have access to the git history of the installer and the requirements. The --dev flag is optional, and can be used to add a couple modules which are useful for Silverstripe CMS development:. Once the create-project command completes, you need to edit the composer.
Another composer update --dev call will now fetch from the development branch instead. Note that you can also convert an existing composer project with these steps. Please read the "Contributing Code" documentation to find out how to create forks and send pull requests. To remove dependencies, or if you prefer seeing all your dependencies in a text file, you can edit the composer.
It will appear in your project root, and by default, it will look something like this:. To add modules, you should add more entries into the "require" section. For example, we might add the blog and forum modules. Be careful with the commas at the end of the lines! However it is relatively easy to tell composer to use development versions. Not only is this required if you want to contribute back to the Silverstripe CMS project, it also allows you to get fixes and API changes early. This is a two step process.
By default, Composer will install modules listed on the Packagist site. There are a few reasons that you might not want to do this. For example:. There are many ways that you can address this, but this is one that we recommend, because it minimises the changes you would need to make to switch to an official version in the future. Composer will scan all of the repositories you list, collect meta-data about the packages within them, and use them in favour of the packages listed on packagist.
To switch back to using the mainline version of the package, just remove the repositories section from composer. Now add an "upstream" remote to the original repository location so you can rebase or merge your fork as required. For more information, read the "Repositories" chapter of the Composer documentation. Generally, you should keep using the same pattern of branch names as the main repositories does. If your version is a fork of 4.
Otherwise, the dependency resolution gets confused. Sometimes, however, this isn't feasible. For example, you might have a number of project forks stored in a single repository, such as your personal GitHub fork of a project.
Or it might just be confusing to other team members to call the branch of your modified version 4. In this case, you need to use Composer's aliasing feature to specify how you want the project branch to be treated, when it comes to dependency resolution. Open composer.
0コメント