Sonya*

Just to mention. I have not found a trigger for "when a CMS record is published". Everything can be prepared in Pages: topics, posts, events, blog entries, files, gallery images, members, comments, reviews etc. If there were a trigger to create another item when the record is published, then this would solve this topic as well. This way we could schedule anything just by creating records in hidden databases and setting a future published date. Unfortunately, it is not possible with Zapier. I have ended up writing a custom app to accomplish it.

They had indeed 150000 hours to develop all the features they had in the last 6 years. There were plenty of them. If they had implemented this one and had abandoned another one in favor of this, then there would be another suggestion topic. The topic with the feature that had been abandoned because of this one. And the customers complain the feature has been ignored for years. 😉

It's not fair what you say. They listen and have to decide what to develop first. Imagine, they have a long list of features and requests. They cannot implement all of them at once. They have to prioritize. Some of the features are at the end of the list. And probably will not be implemented ever. That's life. And while they are developing one feature all others should just wait (waiting is different from being ignored). Errors are solved in the Help & Support forum. I have not seen one that has been ignored. I use the support forum a lot and the most errors I have reported have been solved in the next release. I wish there were a feature for everything I will ever need. And that - out of the box. I have to admit, there is no software out there that has it. I can complain, I can demand, I can develop or job out mods, I can use workarounds, I can make feature suggestions and wait. There are a lot of ways. But saying they ignore and they would listen only to Cloud customers is just not fair.

Then good luck and patience while waiting for solution 🙃

I would contact the developer of the mod first. If there is an issue, it would help him to fix it (not only for you but for everyone). If the developer does not react at an appropriate time then ask for a refund by IPS.

Do not edit hard-coded files, they will be replaced with the next upgrade. You can use the UPGRADING_PAGE constant to specify the location of a new file. See how to use constants.php

I have a database with over 1000 records that are all scheduled to be published in the future. I would like to trigger a Zap only WHEN a record is published. The Zap should not be triggered if the record is just created to be published in the future. It is possible? The action in Zap should create an event in the calendar in another IPS community. The record image should be used as an event cover. I do not see the cover field for the event in ZAP. So, not possible? The actions in Zap are to create a new member AND create a new event with this member as an author. I do not see a possibility to refer to the previous action in Zapier, where I can pick the member created in the previous step. The action in Zap should just execute a custom hook in another community, where I manually define what should happen. Possible? Generally, is Zapier the right way to create all these actions? They are all bound on record publish in IPS. In the record itself, all the fields for creating another content item are set. Zap seems to be not enough, as it misses fields, like image fields or dependencies from previous steps. Probably, is the combination of custom hook onPublish() and REST API still the best way to solve it?

Maybe. Still, I will not able to upgrade if I am IN_DEV, even with an upgrader within the ACP. I wish the same would happen if I am in designer mode 🙂

Thank you all! Me getting continuous help.

What would happen if I install another language in the future. Will this CSS be loaded twice? 🤔

Use case I have created a Pages database similar to Providers. This database has a select field, where the provider can choose a language for communication, e.g. German, Russian, Ukrainian. I would like to display their language selection in template as flags.

I try to display flag icons in Page templates. E. g. for German <i class="ipsFlag ipsFlag-de"></i> It does not work and displays nothing. The reason is, that I do have only one language installed. In system/Dispatcher/Standard.php you do not load a CSS in this case: if ( \count( \IPS\Lang::languages() ) > 1 ) { \IPS\Output::i()->cssFiles = array_merge( \IPS\Output::i()->cssFiles, \IPS\Theme::i()->css( 'flags.css', 'core', 'global' ) ); } What is the reason for not loading this CSS on the projects with only one language installed?

I am not sure what requirements/health check screen you mean. It does not prompt. When I click on Confirm Upgrade on this screen, then the upgrade is started without any warning.

How to reproduce: Go to AdminCP Create New Block and choose custom (Content Editor: Editor) Add some text Add a block via Block Manager on (a) Forums and (b) Database Page I have switched to the default IPS Theme for the test. The result is the same. It has a background in forums and no background in Pages. And I do not know how to delete the background from the block without custom CSS or a 3-rd-party plugin.

It is an default theme customized in easy mode editor. You can reproduce it on invisionify.com The credentials are valid.

I have created a custom block (WYSIWYG) with some text. The block looks different depending on where I place it with Block Manager. In Forums, it has a white background: In Pages, it does not have a white background Questions: Is it possible to create a WYSIWYG-Block that looks the same on every page? Is it possible to remove the white background on the block, when placed in Forums? I need a solution without custom CSS (the blocks will be added by the community manager without CSS knowledge). A custom plugin is not possible as this is a Starter cloud package, where custom plugins are not allowed.

I accidentally upgraded while in Designer Mode (localhost). There was no warning like for IN_DEV. As a result, I have lost some templates customizations. They were on disk, but not in the database. I know, that I should not upgrade in Designer Mode 🙂 But I wish the software would warn me about it in case I am not aware Designer Mode is still on. 🙂

You can ask @Makoto if his app prevents post before register with invalid mails.

I would give a reciprocal database a try. Manage specialities in one database. Add a database relationship field to the doctors, where multiple specialities can be choosen. Enable cross linking.

You would not use categories in this case, but create a database filter to show records from the same "category". It is a workaround. Just to mention, copying a record sounds like awful idea for me. Managing the same record in different places... Duplicate content...

Multiple categories are not possible in Pages. Possible workarounds to assign a record to multiple "categories": Custom Field: Checkbox Set Custom Field: Select with multiple selection Tags

Do you have the same error? Do you use the default XAMPP installation? The error on the screen above shows that no database user was provided. For default XAMPP installation: database host: localhost database user: root database password: [leave it empty]

I see. I use a different e-mail address for outgoing e-mails. This is a kind of noreply@mycommunity.com. This e-mail does not accept any e-mails. That's why I do not see any Mail Delivery Failure from those who use invalid mails. Incoming mails go to a fully functional e-mail address. Probably this is an approach for you.