Marc

As mentioned above, this is a customised pages database, rather than the blog application

I have created a ticket for you on this

Thank you for letting us know. I will flag this up internally

You would need to select the renewal term at the bottom there to be monthly, after selecting buy now on your trial

Just to note, there is an exception to this. If there are lots of followers, these would be queued. However even then, unless you have a lot of other items before them in the queue task, they would go out relatively quickly.

We cannot switch a trial back on after its free trial period unfortunately. What I can say is I cannot replicate the issue you are having locally, so it can only really be that of setup. If albums have to be used per your gallery setup, it does ask. All we can say at this point is to let us know if you see the same issue once live

Glad to hear the issue was found for you 🙂

Are you not seeing the issue on your live instance there?

You could try deleting the contents of your datastore folder. Maybe check what the full error is in your uploads/logs folder too. The other thing you could do, if our record are correct, is upload a fresh set of files and upgrade to the latest release. Other than that, we would need access to advise further.

I will move this to our community support forums, as this is not something we would assist with as part of support.

We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you.

Unfortunately not. What you are looking for there is quite a unique thing. Generally duplicating content would be seen as a bad thing. Could I ask here, if you are thinking of duplicating it elsewhere, what the difference is to them seeing the original? I guess what Im asking here, is what are you trying to achieve?

It's the announcements block you have placed at the top of your site. That is what is breaking your layout.

No problem at all, Todd.

Yes, your current community can indeed be transferred over to our cloud environment. I will get a ticket created for you for our sales team, who are better placed to discuss specifics with you. Based on what you have said there, you can then simply concentrate on running your business, rather than thinking about backups, mysql etc.

You have that block on all themes, not just default. So you would indeed have that issue everywhere

As mentioned, there are quite a few to go through at present, so they can take a while to be approved

In this case the broken html is in your Page builder block at the top. You need to review that code

Where is it you are seeing this? I am not seeing any issues with your site at present

You would click to create a new theme. If you do this, you create a default unaltered theme

It is worth asking, have you ever considered our cloud solution? If you are not knowlegable in anything related to your hosting, including backups, it may be a much better direction for you. You would never need to think about things like this again. You just think about running your site instead

There is no way I would know if those are your mysql database backups for your IPS site. You would not see PHP files on a mysql backup

Feel free to try this. Note, this is outside the scope of support. -- -- Table structure for table `core_achievements_log_milestones` -- CREATE TABLE `core_achievements_log_milestones` ( `milestone_id` bigint(20) UNSIGNED NOT NULL, `milestone_member_id` bigint(20) UNSIGNED NOT NULL, `milestone_rule` int(10) UNSIGNED NOT NULL, `milestone_log_id` bigint(20) UNSIGNED NOT NULL, `milestone_type` varchar(100) COLLATE utf8mb4_unicode_ci DEFAULT 'subject' ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -------------------------------------------------------- -- -- Table structure for table `core_alerts_seen` -- CREATE TABLE `core_alerts_seen` ( `seen_alert_id` int(11) NOT NULL, `seen_member_id` int(11) NOT NULL, `seen_date` int(11) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -------------------------------------------------------- -- -- Table structure for table `core_content_featured` -- CREATE TABLE `core_content_featured` ( `feature_id` int(11) NOT NULL, `feature_content_id` int(11) NOT NULL DEFAULT 0, `feature_content_class` varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `feature_content_author` int(11) NOT NULL DEFAULT 0, `feature_date` int(11) NOT NULL DEFAULT 0 ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -------------------------------------------------------- -- -- Table structure for table `core_editor_stored_replies` -- CREATE TABLE `core_editor_stored_replies` ( `reply_id` int(11) NOT NULL, `reply_title` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL, `reply_text` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL, `reply_added_by` int(11) NOT NULL, `reply_enabled` tinyint(3) UNSIGNED DEFAULT 0, `reply_position` int(10) UNSIGNED DEFAULT 0 ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -------------------------------------------------------- -- -- Table structure for table `core_follow_count_cache` -- CREATE TABLE `core_follow_count_cache` ( `id` bigint(20) NOT NULL DEFAULT 0, `class` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `count` int(11) NOT NULL DEFAULT 0, `added` int(10) UNSIGNED NOT NULL DEFAULT 0 ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -------------------------------------------------------- -- -- Table structure for table `core_item_member_map` -- CREATE TABLE `core_item_member_map` ( `map_class` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL, `map_item_id` int(11) NOT NULL DEFAULT 0, `map_member_id` int(11) DEFAULT 0, `map_latest_date` int(10) UNSIGNED DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -------------------------------------------------------- -- -- Table structure for table `core_item_redirect` -- CREATE TABLE `core_item_redirect` ( `redirect_id` int(11) NOT NULL, `redirect_class` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL, `redirect_item_id` int(11) NOT NULL DEFAULT 0, `redirect_new_item_id` int(11) NOT NULL DEFAULT 0 ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -------------------------------------------------------- -- -- Table structure for table `core_item_statistics_cache` -- CREATE TABLE `core_item_statistics_cache` ( `cache_id` int(11) NOT NULL, `cache_class` varchar(150) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `cache_item_id` int(11) NOT NULL DEFAULT 0, `cache_added` int(11) NOT NULL DEFAULT 0, `cache_contents` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -------------------------------------------------------- -- -- Table structure for table `core_members_logins` -- CREATE TABLE `core_members_logins` ( `member_id` int(11) NOT NULL, `member_date` varchar(10) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `member_timestamp` int(11) DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -------------------------------------------------------- -- -- Table structure for table `core_member_recognize` -- CREATE TABLE `core_member_recognize` ( `r_id` int(11) NOT NULL, `r_member_id` int(11) NOT NULL, `r_content_class` varchar(150) COLLATE utf8mb4_unicode_ci NOT NULL, `r_content_id` int(11) NOT NULL DEFAULT 0, `r_message` text COLLATE utf8mb4_unicode_ci DEFAULT NULL, `r_added` int(11) NOT NULL DEFAULT 0, `r_badge` int(10) UNSIGNED NOT NULL DEFAULT 0, `r_points` int(10) UNSIGNED NOT NULL DEFAULT 0, `r_given_by` int(10) UNSIGNED NOT NULL DEFAULT 0, `r_public` tinyint(3) UNSIGNED NOT NULL DEFAULT 0 COMMENT 'Show this message publicly?' ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- Indexes for dumped tables -- -- -- Indexes for table `core_achievements_log_milestones` -- ALTER TABLE `core_achievements_log_milestones` ADD PRIMARY KEY (`milestone_id`), ADD UNIQUE KEY `lookup` (`milestone_member_id`,`milestone_rule`,`milestone_type`); -- -- Indexes for table `core_alerts_seen` -- ALTER TABLE `core_alerts_seen` ADD UNIQUE KEY `alert_member` (`seen_alert_id`,`seen_member_id`); -- -- Indexes for table `core_content_featured` -- ALTER TABLE `core_content_featured` ADD PRIMARY KEY (`feature_id`), ADD KEY `feature_lookup` (`feature_content_id`,`feature_content_class`,`feature_content_author`); -- -- Indexes for table `core_editor_stored_replies` -- ALTER TABLE `core_editor_stored_replies` ADD PRIMARY KEY (`reply_id`); -- -- Indexes for table `core_follow_count_cache` -- ALTER TABLE `core_follow_count_cache` ADD UNIQUE KEY `id_class` (`id`,`class`(171)), ADD KEY `added` (`added`); -- -- Indexes for table `core_item_member_map` -- ALTER TABLE `core_item_member_map` ADD UNIQUE KEY `map_unique` (`map_class`(171),`map_item_id`,`map_member_id`), ADD KEY `map_lookup` (`map_item_id`,`map_member_id`), ADD KEY `map_member_id` (`map_member_id`); -- -- Indexes for table `core_item_redirect` -- ALTER TABLE `core_item_redirect` ADD PRIMARY KEY (`redirect_id`), ADD KEY `redirect_lookup` (`redirect_class`(181),`redirect_item_id`), ADD KEY `redirect_delete` (`redirect_class`(181),`redirect_new_item_id`); -- -- Indexes for table `core_item_statistics_cache` -- ALTER TABLE `core_item_statistics_cache` ADD PRIMARY KEY (`cache_id`), ADD UNIQUE KEY `cache_lookup` (`cache_class`,`cache_item_id`), ADD KEY `cache_added` (`cache_added`); -- -- Indexes for table `core_members_logins` -- ALTER TABLE `core_members_logins` ADD UNIQUE KEY `lookup` (`member_id`,`member_date`); -- -- Indexes for table `core_member_recognize` -- ALTER TABLE `core_member_recognize` ADD PRIMARY KEY (`r_id`), ADD KEY `r_member_id` (`r_member_id`), ADD KEY `r_content` (`r_content_class`,`r_content_id`); -- -- AUTO_INCREMENT for dumped tables -- -- -- AUTO_INCREMENT for table `core_achievements_log_milestones` -- ALTER TABLE `core_achievements_log_milestones` MODIFY `milestone_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `core_content_featured` -- ALTER TABLE `core_content_featured` MODIFY `feature_id` int(11) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `core_editor_stored_replies` -- ALTER TABLE `core_editor_stored_replies` MODIFY `reply_id` int(11) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `core_item_redirect` -- ALTER TABLE `core_item_redirect` MODIFY `redirect_id` int(11) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `core_item_statistics_cache` -- ALTER TABLE `core_item_statistics_cache` MODIFY `cache_id` int(11) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `core_member_recognize` -- ALTER TABLE `core_member_recognize` MODIFY `r_id` int(11) NOT NULL AUTO_INCREMENT; COMMIT;

I can certainly script out those tables and send them to you (I will do that shortly). You can then attempt to restore them that way and see how you go

You could create a test instance and copy the empty versions of the tables as mentioned, but of course there is no guarantee you wont have issues.