FAQ by topic

English · Deutsch · Home

Daily Scripture adds daily readings, selected Bible passages and personal dashboard widgets to your WordPress website. Choose your sources, shape the design and display readings with Gutenberg, shortcodes, Elementor or Bricks. Website features also work in Multisite, with an additional Network Admin reading view.

Topics

Getting started

What do I need?

WordPress 6.6 or later, PHP 8.0 or later and DOM/XML. ZIP imports require ZipArchive. The plugin can run without a page builder.

Who can manage sources and settings?

The administration pages require the WordPress manage_options capability, normally assigned to administrators. Dashboard reading preferences are personal.

Which output should I choose?

Use Daily Scripture for the official daily readings. Use Bible passage · Daily Scripture for a passage you select from an installed Bible edition.

Are texts already installed?

No. Start with an annual package under Data sources or an edition under Bible library. The plugin ZIP contains software and documentation, not Bible texts.

Can I use multisite?

Daily Scripture 1.0.1 includes Library 0.8.1 with version-aware network approval and a verified handoff during first activation beside an older Library. Website data remains separate; the Network Admin widget uses the selected reference website.

Annual data and downloads

Does checking availability import anything?

No. It lists available source packages. Select the package and start the download/import yourself.

What if a download is unavailable?

Try the source again later or upload its linked original package manually. Have the host investigate TLS or connection errors rather than disabling certificate checks.

Can I replace an installed year?

Yes, with explicit replacement selected. The incoming year is validated before it replaces existing data; a failed validation keeps the previous files.

What happens at New Year?

The active year follows the WordPress timezone. Install the next package in advance. Missing data produces a notice; old verses are not silently reused.

Can I install any Losungen year?

Import and display are limited to the previous, current and next year. Annual packages must include the full year and complete daily pairs.

Bible editions and rights notices

Which editions are supported?

Luther 1912, unrevised Elberfelder 1905, Menge 1939 and Schlachter 1951. Install them individually from the reviewed sources listed in the library.

Are all four sources public domain?

No. The reviewed Luther, Elberfelder and Menge sources are designated public domain. The used Schlachter 1951 source is CC BY 4.0 and retains attribution and its license link.

Does selecting a Bible edition translate the Losungen?

No. Official daily texts stay unchanged and paired. Your chosen local translation is used only for independent passage selections.

Why can a verse number be missing?

Edition numbering differs. Menge combines Ezekiel 33:14–15; select both together. The Schlachter file has no text at Matthew 21:44 and differs in subsequent numbering. The source numbering is preserved.

Keep the notices supplied with each source accessible. Bible 2.0 can present the detailed information in a dialog, with an expandable fallback without JavaScript. Software licensing does not replace text permissions.

Layouts and typography

Where should I start with font sizes?

Choose a layout, then adjust the overall scale. At 100%, the defaults are heading 28 px, verse 22 px, reference 18 px, date 16 px and notices 14 px.

Which layouts are available?

Card, Minimal, Accent, Editorial, Paper, Ribbon, Outline, Divided, Journal and Quiet. The selection cards show their structure; compact density is a separate choice.

Can I use CSS variables from Bricks or Core Framework?

Yes, if they exist on the displayed page and resolve to a font size. Use a fallback such as var(–text-xxl, 28px). The isolated admin preview uses the fallback.

Are relative units automatically responsive?

em, rem and % are relative to their font context, not automatic device breakpoints. Use a responsive CSS variable or the builder’s responsive controls when sizes should change by viewport.

Why does my website differ from the preview?

The preview is isolated from theme CSS and external variables. Check actual theme and builder overrides, element settings and caches. The strict spacing simulation helps, but cannot reproduce every theme.

Where are Gutenberg controls?

Select the block and open the block sidebar. The canvas shows a server-rendered preview using installed local data; each block can override saved defaults.

Can Elementor and Bricks use their own styling?

Yes. Native controls set typography, colors, borders and spacing, including responsive choices. Empty controls inherit plugin defaults.

How do I change headings and the date?

Set source headings in the main settings; blocks and builder elements can override them. An empty date format follows WordPress. Bible 2.0 defaults to Das Wort für heute on German sites and The Word for Today otherwise.

How do I make the dashboard smaller?

Use Display options in the widget to choose compact spacing and a 14, 16 or 18 px verse size. The choice is saved per user and site and does not change the frontend.

Does Bibleserver supply the displayed text?

No. References link to Bibleserver. The target translation is independently configurable and does not change local text.

Backups and stored data

What is included in JSON exports?

Saved design or all plugin site settings. Texts, annual packages, personal widget preferences and builder styles are excluded. Unsaved form changes are not exported.

When does a settings import take effect?

After you review the imported values in the form and save them. Importing the JSON alone does not change the saved design.

Where are annual packages and Bible texts stored?

Under wp-content/uploads/daily-scripture/: data/herrnhuter/YYYY.json.php, data/bible2/YYYY.json.php and bibles/TRANSLATION.json.php. The guide lists each edition’s exact filename.

Does deactivation delete my texts?

No. Deactivation preserves texts and settings. Uninstalling clears temporary caches and scheduled checks. Settings, personal widget choices and texts remain by default. A site’s deletion option removes its settings, preferences and known text files. Physical plugin removal applies each site’s own choice; foreign data remains untouched.

Is JSON enough for a full backup?

No. Also back up the WordPress database, local text directory and any builder templates through your normal backup system. JSON helps transfer settings.

Updates and troubleshooting

How do I install an update?

While the plugin is active, public GitHub releases appear in WordPress Plugins or Dashboard → Updates. No additional updater plugin is needed. Manual installation of the release ZIP also works.

Why is the new version not offered yet?

Successful metadata checks are cached for 30 minutes and failures for 10 minutes. Check again later. Drafts and GitHub prereleases are excluded; hosting restrictions may also block GitHub.

Are automatic updates enabled for me?

No. You decide whether WordPress should install updates automatically. The built-in updater supplies the update information and package.

Why is a Gutenberg preview failing?

Reload the editor and clear relevant browser or builder caches after updating. Check that the selected text data is installed. If it persists, include the exact error and reproduction steps in an issue without credentials.

What belongs in a useful bug report?

Plugin, WordPress and PHP versions, editor and theme, affected source/year or passage, expected and actual result, and repeatable steps. Screenshots help; do not include passwords, license keys or private customer data.

How do I choose widget readings and their website?

Define available readings in Daily Scripture → Dashboard readings: Die Losungen, Bible 2.0 and up to six passages from installed local Bible editions (up to 50 verses in one chapter). Save the website settings, then open Display options in the widget. Select one or more readings and use Move up / Move down to order them. Without JavaScript, numeric positions remain available. No configured readings produces a quiet notice; missing yearly data or an unavailable edition is reported per reading. Personal choices do not change website output. Full JSON settings exports include the reading definitions; design-only and older exports leave them unchanged. Install the required editions on the destination website before saving imported passage definitions.

The Network Admin widget uses a personally selected active website in the current network and visibly names it. When only the main website is active, it is used automatically. With multiple active websites or network activation, select the source website; save once after changing it to load its configured readings, then choose your personal selection. An unavailable previous website falls back with a notice. The network widget is available when the plugin is active on the main website or network-wide; activation only on a subsite does not load it in Network Admin. The website widget switch affects that website’s dashboard; the network reading view is independent. Website choices are paginated in groups of 50. No separate network Bible storage is created.

Color controls use the modern WordPress color picker in a WordPress modal, with direct hex entry and optional text-color inheritance. Changes remain in the form until you save the settings.

For first network activation beside an older Library catalog that still blocks its card, open Network Admin → Plugins → Daily Scripture → Network Activate. The new Library takes over during that native activation. Hosts already running Library 0.8.1 offer activation directly in the catalog.