Skip to content

Commit

Permalink
Fixing spell check warning.
Browse files Browse the repository at this point in the history
  • Loading branch information
milosh-96 authored Feb 18, 2025
1 parent 7383c3f commit 2cb70bf
Showing 1 changed file with 0 additions and 30 deletions.
30 changes: 0 additions & 30 deletions Readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,36 +58,6 @@ For example, if the project you're working is called `Awesome Project`, then you

The [`Piedone/DotNest-Sites` project](https://github.com/Piedone/DotNest-Sites) mentioned above also demonstrates all of these.<!-- #spell-check-ignore-line -->

## Contained sites

The solution also contains the recipes and themes of Lombiq's DotNest Orchard Core sites, these currently being:

- Ik Wil Een Taart

### Ik Wil Een Taart

#### Lucene indices (for local testing)

The lucene index for products have to be rebuilt on the IWET tenant after site setup. You can do that at _/iwet/Admin/Lucene/Index_. After it, you should see 3 products in the _Gebakjes_ menu.

#### Elasticsearch indices

If you want to use Elasticsearch from your machine (`localhost`) you need to set it up first. See: [https://docs.orchardcore.net/en/latest/docs/reference/modules/Elasticsearch/#install-elasticsearch-7x-with-docker-compose](https://docs.orchardcore.net/en/latest/docs/reference/modules/Elasticsearch/#install-elasticsearch-7x-with-docker-compose "https://docs.orchardcore.net/en/latest/docs/reference/modules/Elasticsearch/#install-elasticsearch-7x-with-docker-compose"). The previous step is not necessary if you are using the default Elasticsearch settings in `appsettings.json`. After it you should set up the site with the `IkWilEenTaart.Elasticsearch.Setup.recipe` setup recipe. Finally, you should see 3 products in the _Gebakjes_ menu.

#### Commerce settings

Make sure to set the correct currency on the dashboard, in _Configuration__Commerce__Currency_.

#### Stripe payment

To be able to test Stripe payment, you need to set the Stripe API keys on the dashboard, in _Configuration__Commerce__Stripe API_. You can find the test API keys and test cards [here](https://github.com/OrchardCMS/OrchardCore.Commerce/blob/main/Readme.md).

#### Workflows

Workflows are imported from recipes. Some of them won't work right away, see [this GitHub issue](https://github.com/OrchardCMS/OrchardCore/issues/5490). For `inschrijf_workflow` and `contact workflow` you need to regenerate the URLs. To do that go to the admin dashboard, then to _Workflows_. Click on _Edit_, then click on the _Startup task_ (first one, green colored) and on _Edit_. You can see the URL there, click on _Regenerate_, and then copy the URL. Find where the old URL was used and copy it there.

Currently only one URL is used for workflows. Go to the admin dashboard then _Content__Content Items_. Search for _Contact_, you should see a _Page_ content item, edit it. At the bottom you can see the _inschrijfformulier Formulier_ accordion, open it. Paste the newly generated URL to the _Action_ field, overriding the old one and save the content item.

## Help us make it better

In case you come across an Orchard Core bug during development, don't keep it to yourself: Orchard Core bugs should be reported at [the official Orchard Core GitHub repository](https://github.com/OrchardCMS/OrchardCore).
Expand Down

0 comments on commit 2cb70bf

Please sign in to comment.