How can we help you?

You may be seeing a difference between the different view ports (desktop/tablet/mobile) when viewing your site banner. Don’t worry this is not a bug, this is normal when our top banners are set up. The reason why its cutting off areas of the background image is to prevent the image ratio from scaling when reaching those view ports. This can cause display issues especially when the editable content (text, button & etc) is overlayed on top of the background image. It was set up this way to accommodate the proper display of the banner & ensure that its responsive with our layout.

All images are designed differently or some photos are taken at a different perspective. Unfortunately we don’t accommodate for all these types of images.

If this does not work for you and want to fit the background image to the whole screen on mobile/tablet or modify how the banner is displayed, then you will need to adjust both the HTML & Custom CSS including the media queries to fully customise your experience. You can do this by switching to the HTML Block for the banner. Refer to this blog post regarding HTML Editors on the site: https://www.thrinacia.com/blog/post/how-to-add-custom-code-to-a-section-of-the-site-through-the-html-editor The other option is to update your uploaded image that will best fit this setting.

Adding Google Analytics to your website is simple.

First Create a Google Analytics Account:

Fill out the sign up form.

Next, you will see the code that you will be pasting into your website.

Log into your website, and go to the Administrator Dashboard. Click on Portal Settings –> Website Settings, then scroll down to the Website Footer Code Section

Once your at the Website Footer Code Section, paste the code that Google Analytics provides. Save your changes. You can now view the analytics on your Thrinacia Atlas website using Google Analytics.

If you are experiencing any issues with payments on your platform, and do not know what is causing the issue. It is best for Thrinacia support to look into the issue for you. In order for us to help you, we would require the following:

1. A valid credit card –  This is needed to test the payments (it is only necessary if you are in LIVE mode in your payment settings from the admin dashboard). It is preferred to send us the access details to an account that has previously made a successful payment. As an alternative solution, you can also send us your card details to the Nexus system. You can do this by adding the details to a text file, go to your project, click on the files tab, then click on New file.

We will delete your card details when we are finished with testing.

2. Admin Access to your Stripe account. You can provide admin access to the Stripe account via team member access. Read the following article to learn how to add team member to your Stripe account: https://support.stripe.com/questions/invite-team-members-or-developers-to-access-your-stripe-account

You will have to add dev@thrinacia.com with admin access.

3. How you received the issue. We would need to know the steps that you took to receive the issue. Please include any screenshots or videos if necessary. We will need to know the operating system + version and the browser + version that was used to reproduce the issue.

You can send the information to support@thrinacia.com.

Current Thrinacia Atlas WordPress plugin is a wrapper around Thrinacia Web UI. It is not fully integrated WordPress solution.

The plugin ensures Web UI can easily be activated and run from the predefined website path. It also allows your WordPress website to still function as normal but it reserves its own pre-configured path for Thrinacia Atlas Web UI.

All Web UI files are shipped with the plugin and can be customized as needed. Similar custom development and bundling/build process can be used to build the Web UI for the WordPress plugin. That process is described here: https://www.thrinacia.com/faq/post/how-can-i-make-custom-modifications-to-thrinacia-atlas-wordpress-plugin

Note that Thrinacia Atlas WordPress plugin is not fully integrated into WordPress, so it works in a same way as Web UI. Communication is done with Atlas REST API for your instance, menus will likely need to be maintained on both WordPress and Web UI side and any theming needs to be implemented in the actual Web UI to follow the theme of your website.

Theming changes for the WordPress plugin Web UI can be done by changing AngularJS views/partials/controllers or by adjusting custom CSS in a same manner as customizing the standalone Web UI. That process is described here: https://www.thrinacia.com/blog/post/new-development-workflow

To add embedded code into a campaign, you must first have a campaign made. Edit your campaign, by going to my campaigns.

Then click on edit.

Click on the details tab.

Go to the campaign details section. Click on the code button.

Paste your code in the editor. here is an example:

Remember to save, and the embedded code should appear in your campaign details.

Yes. Even though Thrinacia is geared towards Rewards/Donations/Pre-Sales or Recurring Contributions, equity crowdfunding websites are possible as well with our core technology.

There are configuration parameters that can be applied that allows portal owner to quickly get up and running with their equity crowdfunding website. For full blown or more advanced equity websites, some custom development may be required depending on the requirements. We provide this through our customization or custom solutions path.

If you are looking to add an email token, or fix an email token, here is what you need to do:

First, go to Admin Dashboard –> Portal Settings –> Email Notifications. Choose the email you want to edit, then choose the token you want to add, on the right side of the page. Insert the token.

Next, Click on the code button.

be sure that your token has the opening tag (your selected token) and the closing tag . here is an example of what it should look like:

It should not have any other text. If you see something like this:

Than delete the additional text, remember to save, and the token should work now.

Facebook will normally parse and cache the shared URL for some time. In order to clear facebook cache and tell it to re-parse the URL do the following.

1. Login to facebook
2. Go to Facebook Sharing Debugger, found at: https://developers.facebook.com/tools/debug/sharing
3. Paste URL and click “Debug” button
4. Click on “Scrape Again” button to refresh the facebook cache