There's nothing here yet
Recently Browsing 0 members
- No registered users viewing this page.
By Muddy Boots
If we have a cloud account - and wish to move - can we get a backup easily ?
If so how is this done ? ftp ? file share ?
And also as it looks like all images and such like are on amazon s3 rather than in the dB - how do we get these in the backup ? ie a full backup of everything ?
By Larry Kachadorian
Having a separate test/dev site separate from your "production" environment is pretty much standard practice. Yet for cloud accounts that has presented a problem ... unless we've missed something that is available.
Since transitioning to Invision cloud , in addition to our main site, we have paid for the smallest legacy cloud account as a test/dev site. Its closed to guests , and can only be accessed by accounts that are created by our Admin. We prototyped our site there prior to our actual migration from our previous vendor and have maintained it since.
This second site was/is invaluable in preventing issues ... particularly in one of the major upgrades (4.5 ??) which changed how the default theme handled the header space and made some 3rd party themes as well as some apps unusable. We were able to find out what issues specifically affected our site. And it was huge. If we had just applied it to production, it would have been a disaster.
Same with the initial roll-out implementation of lazy loading . We had images imbedded in the Forum descriptions which caused issues which we caught on our test/dev site. Invision support recognized the problem as somewhat unique to us at that time.
I could go on, but the value that a test/site provides is obvious. Even for small, non commercial sites like ours.
However now that option is going to cost more since Invision is closing out the legacy options with new, more expensive offerings. The increase in cost and "functionality" does not, for us, create any new value. Particularly since our use case for the account has an infinitesimal impact on the Invision host environment.
There should be a fixed, low cost method of providing an option for managers/developers of cloud accounts where than can duplicate their unique production environment for the purposes of testing new apps/upgrades etc.
I want to bring back the latest Events and Topics, but only the ones that a given user is Authorized to see. For both of these endpoints, the only way to do this is to use an oAuth access token.
I don't actually have a third party service that I want to integrate with, the script simply needs to run on my server. I want to get a token to impersonate the user, so I can get this information back. What's the easiest way to generate one of these tokens?
By Jon Erickson
This simple lightweight application allows you to send emails from the Invision Power Board platform through the AWS Simple Email Service API. This application sits on top of your configured email delivery methods and overrides your default settings. With the click of one button, enable and disable the service. The application also features several complaint and bounce management actions that may be applied to members to help improve throughput and deliverability.
Amazon SES is one of the most robust and cheapest transactional email service providers on the market. While this application is extremely lightweight and easy to configure, most of the work to correctly set up will occur within the AWS Console. Follow the following steps to correctly configure AWS to send emails.
NOTE: When you initially begin to use AWS Simple Email Service, you will be in a non-production, sandbox environment allowing you to test the email service without affecting your deliverability and reputation. Once you are ready to enter production, you will need to request access from AWS under the Sending Statistics section. The form is self-explanatory and will not be covered here.
Feature Requests and Bug Reports: Click here to file a bug report or suggest a feature for our development team.
Support Topic: Click here to read the Invision Power Board support topic.
View AWS Simple Email Service Pricing
Simple Email Service Installation For Sending Emails:
Create or Sign In to your AWS Console. Proceed to the IAM section of the AWS Console. On the left, select the Users section and add a new user. If you already have a user you would like to use, proceed to the next step. Enable programmatic access for the user account. Attach the AmazonSESFullAccess policy to the user account. Finish creating the account, adding any tags you'd like for easy identification. Copy and paste your Access Key and Secret Key into the corresponding fields within the Invision Power Board ACP settings. Proceed to the AWS Simple Email Service section of the AWS console. Select your closest region in the top right corner. Copy the corresponding region identifier and input it into the corresponding field within the Invision Power Board ACP settings. Save your Invision Power Board ACP settings. Back within the AWS Console, select Domains -> Verify a New Domain to add the domain you wish to send emails from. This is called Verified Identities - Add Identity, if you are using the new AWS console. You may enter as many email addresses as you wish to send email from. Make sure to check the "Generate DKIM Settings" checkbox. These are enabled by default if using the new AWS console. This will help with your deliverability. Update your DNS records for the domain you are verifying by adding the TXT and CNAME records that are presented. Make sure to not update the MX records as this will affect your ability to receive the emails. We are only configuring sending emails. For each verified identity you add, enter the same email address in the corresponding field of your Invision Power Board ACP settings. Once an email address has been verified, you are ready to start sending emails. Fill in the Default Sending Email Address field of your Invision Power Board ACP settings. This will help your Invision Power Board website not send emails from unverified domains. This may happen through third-party applications. While in the sandbox environment, you will need to add your test receiving email address under the Email Addresses section, or else you will receive a sending error. Once everything is configured, proceed back to the Invision Power Board ACP and proceed to Email Settings. You can use the built-in Test Email Settings feature to test AWS SES. You will see the corresponding logs under the AWS SES application and any generated errors. Simple Notification Service Installation For Handling Bounces/Complaints:
Create or Sign In to your AWS Console. Proceed to the IAM section of the AWS Console. Select the user that you created/or designated when setting up Simple Email Service for sending emails. Attach the AmazonSNSFullAccess policy to the user account. Proceed to the AWS Simple Notification Service section of the AWS console. Create two new topics for handling bounce and complaint notifications, one for bounces and one for complaints. Make sure these are Standard topics. Name them for easy identification. Proceed to the AWS Simple Email Service section of the AWS console and click on your Verified Identity/Domain used in sending emails. Click the Notifications tab and edit the Feedback Notifications. Select your newly created SNS topics for their respective field. Make sure to "Include original email headers". Once your domain notifications are set, proceed back to your Invision Power Board ACP settings and proceed to the REST & OAuth section. Create a new API key and make sure to allow access to all endpoints under the AWS Simple Email Service application. Enable logging for both endpoints as well. Once you have created the new API key, click on the API reference tab and copy the example API POST URL for each AWS Simple Email Service endpoint; bounces, and complaints. Proceed back to the AWS Simple Notification Service and create a new subscription. You will create two subscriptions as well, one for bounces and one for complaints. Choose the matching topic and select HTTPS for the protocol. Paste the appropriate API POST URL you copied from step 11 and attach the ?key=APIKEY query parameter to the end of the URL. For example, the entire URL should look something like: https://community.deschutesdesigngroup.com/api/awsses/bounces?key=APIKEY. If you do not utilize Friendly URL's (the default setting), you may have "index.php" in your URL. Make sure to create a second subscription for complaints - you should have two subscriptions, one for bounces with the bounce API URL and one for complaints with the complaints API URL. The AWS Simple Email Service application will take care of confirming the subscription for you. If the subscription does not show Confirmed, your API endpoint may not be configured correctly and you should submit a support ticket for assistance. AWS should now post a notification every time a bounce and complaint is encountered and Invision Power Board will process the notifications based on the email address using the Bounce and Complaint settings saved in your ACP settings. Bounce and Complaint Notifications can be tested by sending a test email through Invision Power Board's Test Email function to firstname.lastname@example.org and email@example.com. Logs for each notification should be seen in your settings.
By Neda Niquie
I was experimenting with my new cloud-hosted community, and things got messed up.
I can't seem to revert, and clear cache didn't help.
The styling in AdminCP is messed up, default theme styling is messed up, default-profile-images are gone, etc.
Can I get a 'revert', or a fresh install install please?