-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ English
- Getting started
- Annual data and downloads
- Bible editions and rights notices
- Layouts and typography
- Editors, links and dashboard
- Backups and stored data
- Updates and troubleshooting
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.
The administration pages require the WordPress manage_options capability, normally assigned to administrators. Dashboard reading preferences are personal.
Use Daily Scripture for the official daily readings. Use Bibelstelle · Daily Scripture for a passage you select from an installed Bible edition.
No. Start with an annual package under Datenquellen or an edition under Bibelbibliothek. The plugin ZIP contains software and documentation, not Bible texts.
Activate separately on each site. Network activation is not supported; each site receives its own data directory.
No. It lists available source packages. Select the package and start the download/import yourself.
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.
Yes, with explicit replacement selected. The incoming year is validated before it replaces existing data; a failed validation keeps the previous files.
The active year follows the WordPress timezone. Install the next package in advance. Missing data produces a notice; old verses are not silently reused.
Import and display are limited to the previous, current and next year. Annual packages must include the full year and complete daily pairs.
Luther 1912, unrevised Elberfelder 1905, Menge 1939 and Schlachter 1951. Install them individually from the reviewed sources listed in the library.
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.
No. Official daily texts stay unchanged and paired. Your chosen local translation is used only for independent passage selections.
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.
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.
Card, Minimal, Accent, Editorial, Paper, Ribbon, Outline, Divided, Journal and Quiet. The selection cards show their structure; compact density is a separate choice.
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.
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.
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.
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.
Yes. Native controls set typography, colors, borders and spacing, including responsive choices. Empty controls inherit plugin defaults.
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.
Use Ansicht anpassen 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.
No. References link to Bibleserver. The target translation is independently configurable and does not change local text.
Saved design or all plugin site settings. Texts, annual packages, personal widget preferences and builder styles are excluded. Unsaved form changes are not exported.
After you review the imported values in the form and save them. Importing the JSON alone does not change the saved design.
Under wp-content/uploads/daily-scripture/: herrnhuter/YYYY.json.php, bible2/YYYY.json.php and bibles/TRANSLATION.json.php. The guide lists each edition’s exact filename.
No. Deactivation preserves texts and settings. Uninstalling removes plugin settings and personal widget choices; known text files are deleted only if the removal option was enabled.
No. Also back up the WordPress database, local text directory and any builder templates through your normal backup system. JSON helps transfer settings.
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.
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.
No. You decide whether WordPress should install updates automatically. The built-in updater supplies the update information and package.
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.
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.
Daily Scripture
Deutsch
English