Advanced settings
This screen is for experienced administrators who understand the site’s deployment and existing public URLs.
If you want to change a logo, menu label, phone number, or paragraph, you are in the wrong place. Use Appearance, Contact, or the relevant content page. An unfamiliar value here is not a request to fill it in or make it more readable.
Admin path: Website > Settings, then Advanced settings at the top of the screen
Route:/instance/advanced
Domain and route changes can break login, deployment, bookmarks, and search results. Record the current values and arrange technical review first.
The screen has four boxes: Images, Domain, Email, and Route management. Select Save at the bottom to store changes from all of them.
Image sizes
Image sizes lists extra image dimensions the website should generate from uploaded media. Its hint warns you to change it only at your own risk, because it can break the website.
Enter one size per line, in the format the developer gives you. These sizes are added to JORD’s built-in sizes.
These are sizes of generated image copies used by the website, not the number of pictures on a page. Do not change them to correct one badly cropped photo. Check that photo’s ratio or choose a different image in its content editor first.
Changing a size does not guarantee that old uploads will be regenerated. Confirm the deployment’s media process before changing a live site.
Domains and email identity
| Field | What it is |
|---|---|
| Default domain | The public website domain. It is required. |
| OAuth 2.0 domain | The domain the site uses for sign-in. When empty, the field shows oauth2. followed by the default domain as a placeholder. |
| Issuer | The account or tenant boundary used by authentication and data ownership. When empty, the field shows http:// followed by the default domain as a placeholder. |
| Sender email | The address JORD sends notifications from. It is required. |
| Sender name | The name shown with those notifications. |
The domain and issuer hints carry the same warning: change them only at your own risk, because they can break the website. Leave them unchanged unless the person maintaining the website gives you the exact replacements. The default domain is not the title shown in the browser. The OAuth domain belongs to the sign-in setup, and the issuer identifies the configured account or tenant. Do not invent replacements for either.
The sender address is used for contact-form enquiries and for newsletters. It is separate from the inbox receiving contact-form enquiries. Change the recipient under Features > Contact form, not here. A sender change may also require work in the email service.
Content routes
Route management lets you replace the default public URL part of some content types. It covers these entries:
| Entry | Can be disabled |
|---|---|
| Article | No |
| Reference | No |
| Contact page | Yes |
| Cookie settings page | Yes |
| Event | No |
| Imprint | Yes |
| Team member | No |
| Privacy policy | Yes |
| Product | No |
| Product list | Yes |
| Service | No |
| Service list | Yes |
| Event series | No |
Pages, categories, and other content types do not have an entry here.
Each entry works the same way:
- Turn on the entry’s Override default route checkbox, for example Override default article route.
- For entries that can be disabled, decide whether to turn on Disable default route, for example Disable default contact route. This turns off the default route for that page and hides the language fields.
- Otherwise, fill in one route field for each saved website language, such as Hungarian article route.
The language fields follow the languages saved under Appearance > Website languages. Save a new language there before you look for its route field here.
Before changing a route:
- List the public URLs that use it.
- Plan redirects for the old URLs.
- Check navigation, footer, sitemap, and external campaign links.
- Save the new route.
- Test list and detail pages.
- Confirm redirects and search settings.
If the deployment does not support the needed redirects, keep the current route until a developer adds them.
Ask for a technical change
You do not need to understand every field to request help. Tell the website administrator what visitors should experience, such as “Our public domain is changing” or “Old article links must keep working”. Include an example public URL and the intended replacement, if known.
Before a change, have them record the existing values, confirm a recovery plan, and agree when to test it. Afterward, check public pages, login, and outgoing email as appropriate. If a route or domain change breaks access, use your separate support contact rather than trying more values until something works.