Solution home Forms Form Configuration

Form is not being displayed or shows an error message

Modified on: Wed, 10 Apr, 2024 at 12:20 PM

INHALTSVERZEICHNIS

Learn in this article possible reasons why your FundraisingBox donation form is not displayed as expected on your website.

Javascript Compatibility

Your Content Management System (CMS) must fundamentally support the integration of JavaScript code. To check this, you can embed the following code in the backend on the donation page:

<script type="text/javascript" src="https://www.fundraisingbox.com/assets/js/jstest.js">

When you visit the page, a note will appear in the browser whether JavaScript is activated and thus the form can be embedded.

Note: There are various CMS products or CMS functions/configuration options that do not insert the donation form embedding code into the source code of the subpage you want!

Instead, the following happens:

  • Your CMS uploads the form code to a CDN (Content Delivery Network)
  • From there, the form code is loaded when your website itself is loaded
  • This results in the embedding address of the form code not matching the embedding address you have specified in the configuration of the donation form in your FundraisingBox (more on the topic of embedding address below)
  • Therefore, it is possible that the basic JavaScript test described above appears successful, but the FundraisingBox donation form is then not displayed as expected on your website
  • Instead, an error message may be displayed indicating that the embedding address of the form code does not match
  • To find out how you can embed the form code directly into the desired subpage of your website in such cases, you may need to contact your CMS provider directly

Embedding Address

Error message: The stored embedding address does not match this address. Please correct these settings in your FundraisingBox.

1. Embedding Address Please first check whether the embedding address you have stored in your FundraisingBox actually matches the web address where the form is to be displayed:

2. Multiple Domains If you have multiple domains for the same website, e.g., www.sample-organization.de  and www.sampleorganization.de , please contact our Support so we can activate this special case. The same applies if you use multiple addresses for the same page with identical content (including language), e.g., www.sampleorganization.de/index.php?id=123 and www.sampleorganization.de/donate.html .

Note: If the pages have different content, a separate form with its own embedding address must be used. If you have any questions, please feel free to contact our Support.

3. Form in Frame Pages It is not technically directly and immediately feasible to use FundraisingBox forms or donation campaign tools within frame pages or iFrames. Embedding on such pages can therefore cause this error message. This has several reasons:

  • the automatic size adjustment does not work
  • the pre-filling of fields is not feasible
  • after a successful transaction, the donor is sent back to the embedding address, so the content outside the frame would be no longer visible

Frame pages are an outdated technology, which are also not optimal for search engines. If these pages of your website are not converted, it is best to link to your donation form on a separate page in this case. You can also create buttons and widgets with the FundraisingBox Button Generator.

Error message: The FundraisingBox logo was not correctly integrated.

1. Embedding Address Also with this error message, please first check whether the embedding address you have stored in the FundraisingBox actually matches the web address where the form is to be displayed.

 2. FundraisingBox Logo Check All online forms and donation campaign tools of the FundraisingBox are provided with a small gray logo of the FundraisingBox including a link to our website in the bottom left area. Displaying the logo is mandatory according to section 4.4.1 of the FundraisingBox Terms and Conditions. All FundraisingBox forms are automatically checked. If the logo is not displayed, for example due to changes to the embedding code or the use of additional code, the form itself will also not be displayed, and you will receive the corresponding error message. Therefore, always use the complete embedding code provided for each donation form in your FundraisingBox under Forms > Select Form > Embed Code. The embedding code must be inserted into the embedding webpage 100% EXACTLY as you find it in your FundraisingBox when the embedding page is loaded in the web browser.

Note: Content Management Systems (CMS) like WordPress, Typo3, etc., may automatically modify your website's code without your intervention. This can result in image files like the FundraisingBox logo being uploaded to a CDN (Content Delivery Network) and the actual URL of the logo (https://secure.fundraisingbox.com/images/FundraisingBox-Logo-Widget.png) being replaced by a URL with the domain of the CMS. If this is done, the logo check will fail and the donation form will not be displayed. To correct this, the corresponding function (CDN upload of image files, etc.) must be deactivated in the CMS – at least for the FundraisingBox donation form embedding code. For more information, please contact your CMS provider.

3. Lazy Loading (Delayed Loading of Images)

If the above points do not apply to your case and the form is still not displayed, please check whether your page or CMS uses so-called "Lazy Loading" for images. This can cause images to be loaded only when they or the frame of the FundraisingBox donation form are visible in the viewport (currently visible section of the website in the browser). The FundraisingBox logo or the frame of the FundraisingBox donation form is therefore not visible or not loaded when the logo check occurs. This is why the corresponding error message appears. Normally, images can be excluded from lazy loading and loaded immediately. If you have specific questions about this, please contact your CMS support or the person responsible for the administration of your website or web server.

Possible solutions include:

  • Lazy Loading (as a WordPress Plugin)  Check the source code of the website where the FundraisingBox donation form in question was embedded to see if code strings like lazy, lazy-load, etc., appear. In this case, you can replace your embedding code with the following code or add the CSS class no-lazy as shown below: <script type="text/javascript" src="https://secure.fundraisingbox.com/app/paymentJS?hash=znvuzy0at8p5bt8y"></script><noscript>Please activate Javascript</noscript><a href="https://www.fundraisingbox.com" target="_blank" rel="noopener noreferrer"><img class="no-lazy !important;" style="border: 0 !important;" src="https://secure.fundraisingbox.com/images/FundraisingBox-Logo-Widget.png" alt="FundraisingBox Logo" border="0" /></a>    Please replace the red highlighted hash valuein the code above with the hash value from your own embedding code!

    Note: If the error message and the FundraisingBox logo are displayed together, then please examine the FundraisingBox logo by right-clicking to check the actual web page code loaded in the browser for lazy-load CSS classes on the HTML elements.

  • Issues with Action Link Plugin (in WordPress) WordPress plugins, such as Action Link, add additional images in the form of links to the <a> HTML element of the FundraisingBox logo at the end of the donation form. The FundraisingBox logo check may then fail. The form may be briefly loaded and displayed, but then replaced by the corresponding error message. The source code of the website or the embedding code of the donation form in the FundraisingBox may not be comprehensible! The website displaying the donation form must be loaded in the browser and the FundraisingBox logo element examined there. In this case, please check the code (e.g., in Chrome via Right-Click > Inspect on the FundraisingBox logo). An example of faulty code looks like this:
<a target="_blank" href="https://www.fundraisingbox.com <https://www.fundraisingbox.com>"class="exitNotifierLink"role="link"><img border="0" style="border: 0 !important" src="https://secure.fundraisingbox.com/images/FundraisingBox-Logo-Widget.png <https://secure.fundraisingbox.com/images/FundraisingBox-Logo-Widget.png>" alt="FundraisingBox Logo">&nbsp;<img class="flat" src="https://testdomain.de/wp-content/plugins/exit-notifier/external-link.png <https://testdomain.de/wp-content/plugins/exit-notifier/external-link.png>" border="0"></a> The correct code looks like this: <a target="_blank" href="https://www.fundraisingbox.com <https://www.fundraisingbox.com>"><img border="0" style="border: 0 !important" src="https://secure.fundraisingbox.com/images/FundraisingBox-Logo-Widget.png <https://secure.fundraisingbox.com/images/FundraisingBox-Logo-Widget.png>" alt="FundraisingBox Logo"></a>

FundraisingBox components such as the donation form are web applications and require so-called local storage, which is created on the device of the donors to process data, e.g., personal data, donation amount, donation interval, etc.

Local storages are only created when a website is opened where a FundraisingBox component is embedded and intended to be displayed, and are deleted immediately upon leaving or closing the relevant website.

There are Cookie Consent Managers, e.g., the Consent Manager from Cookiebot, that do not distinguish between cookies and local storage, consequently do not categorize local storage correctly, and then block it. Therefore, FundraisingBox components may not be correctly displayed if such Cookie Consent Managers are used. In this case, please contact the provider of your Cookie Consent Manager.

A workaround could also be to enclose the embedding code of the relevant FundraisingBox component in the code of the website in a Div container, for example, and exclude this Div container from the rules of the Cookie Consent Manager. However, this solution is not clean and therefore not recommended.

Note: Implementation of the above-described workaround is at your own risk!

Did you find it helpful? Yes No

Can you please tell us how we can improve this article?

More articles in Form Configuration