Update itunes owner Email in RSS feed - rss

We have generated one RSS feed and submitted to itunes few months ago. Now we realised we have added the wrong email. So can we update the email id in our rss feed? If we update in our rss feed, Do we need to submit again? please let us know about this. Thank you.
<itunes:owner>
<itunes:name>FeedForAll</itunes:name>
<itunes:email>abc#abc.com</itunes:email>
</itunes:owner>

Here is a snippet from Apples's doco on podcast rss feeds...
<itunes:owner>
The podcast owner contact information.
Include the email address of the owner in a nested <itunes:email> tag
and the name of the owner in a nested <itunes:name> tag.
Note: The <itunes:owner> tag information is for administrative
communication about the podcast and isn’t displayed in Apple Podcasts.
Please make sure the email address is active and monitored.
Once Apple has verified the ownership and quality of your rss feed (i.e. through the podcast submission process) then your podcast is active in their directory.
From that point you are free to update your feed however you like, as long as your updates continue to conform to Apple's rss feed requirements.
In this case, if you update the value of the <itunes:email> then the change should automatically be picked up during the next feed refresh. i.e. you shouldn't need to resubmit.
Note: you should still use a valid email address in that tag so that people can contact you if there are issues with your feed, or they genuinely want to get in touch, etc. If you are worried about spam, then perhaps use an email address that different from your day-to-day address. i.e. One that you can access/check when you need to but that won't bother you if it gets hit with spam. You can drop in there and check it/clear it out occasionally as needed.
Also worth thinking about. Other podcast directories sometimes rely on email addresses in rss feeds in order to verify ownership. E.g. this is how Google uses it...
Step 3: Verify ownership
After you’ve submitted your RSS feed, review the email address used to
verify ownership of your podcast. To verify that you own the podcast
content you’re adding, you need to have an email address in the
<googleplay:email> or <itunes:email> field of your podcast’s RSS feed.
Click Send verification code. Check the email account listed for your
verification email. Visit the link included in the email to complete
the verification process.

Related

youtube api members map to wordpress users

I have a wordpress website that uses woocommerce memberships.
We somehow managed to map patreon users to woocommerce memberships so that they get all the perks via our own website.
I know it's possible to query the Youtube API endpoint members.list which would give us 1) the membership level and
2) the youtube channel id of each individual member
How can we then validate that a wordpress user is a youtube valid member?
With patreon the validation is by matching email address, but on youtube there's no access to the user email. I guess the user would have to set his youtube channel id in our website so we can later confirm it matches a valid membership.
The problem is that anyone can provide someone elses channel id to trick the system...
any ideas that would help with this much appreciated
If I were you I would generate a token for each user on your website, such that if they put this token in their channel description (ABOUT tab) then you can be sure that the given YouTube channel owns the given account on your website where he got his random token. You can get their channel description by using this reverse-engineered YouTube UI solution.
You can also think of other mechanisms such as requiring the user to post a comment on a video and checking using YouTube Data API v3 CommentThreads: list endpoint or post a message on a livestream and checking using YouTube Live Streaming API LiveChatMessages: list endpoint.
Note that depending on your token format, it may be useful to use an unusual pattern to put in their channel descriptions to avoid wrong authentication (a channel description containing unintentionally a token assigned to a user by your website). For instance if you assign an id (0, 1 and so on) to each user (or if you just use their usernames) just requiring this id to be in the channel description isn't very secure as anyone may put unintentionally someone else token. What you can do while still avoiding random token is to use a prefix. That way your website won't just look for 0, 1 and so on in their channel description but instead Your website: 0 or Your website: 1... Using a prefix keeps user-friendliness (Your website: Benjamin Loison looks better than 77ff716cfdd4e7ed) while being quite secure.

Sending informaton to a sage pay payment gateway

I have product designer software in my website that currently allows customers to design a product and get a live price. The software has the ability to send a message to the parent of an iframe where the information can be processed as I like. I want this information to be sent to my sagepay, worldpay or stripe payment gateway to give the customers the ability of purchasing the product.
Does anyone have any idea how to achieve this or even where to start!
Thanks in advance
Dan
Most payment gateways allow somehow to send the details of the purchased products details via API when processing the payment.
For SagePay (if you mean the one which currently is labeled as Opayo by Elavon) you may use the detailed basket via XML or CSV. Or you may simply use the common Description field.
For Worldpay it's the instruction.narrative.line1 field from the authorization request.
And for Stripe it should be either metadata or payment_intent_data objects.

How to enable already subscribed users subscribe again to the Mailchimp/Aweber/GetResponse list

I'm creating website in WordPress. Idea is to show users sign up email subscribe form in welcome page and when user subscribes they redirects to home page, but user can't go to the home page second time because he/she already subscribed.
I cannot speak for GetResponse or MailChimp, but AWeber automatically prevents people from signing up to your list a second time. If you'd like, you can set a custom already subscribed page from within a sign up form created with our generator. You can find directions for that here:
https://help.aweber.com/hc/en-us/articles/204027726-How-Do-I-Set-an-Already-Subscribed-Page-
If you're using our API to add subscribers from your site, we will give back a 400 response with the message "Subscriber already subscribed." should you try to add someone that's already on your list. You could catch that exception and direct the user to your already subscribed page or to your homepage.
We do not monitor StackOverflow on a daily basis, so if you have further questions regarding our API, please reach out to us at api#aweber.com for more assistance, as that inbox is monitored daily. For general account inquiries you can contact help#aweber.com to reach our Customer Solutions team.
Kaitlyn C.

Shopify checkout process

Shopify used to allow you to style the checkout process through a CSS file. However, they have now removed this option.
I've developed a Shopify App for a customer that requires that ALL customers digitally sign a form before payment. The form asks specific questions, and must be presented in a specific way, with a specific font. In their country it is illegal to sell online without sending your customers through this process. Everything is sent over TLS etc.
On the form, a customer is asked their name, delivery address, billing address, etc. The products are listed and followed by a ton of legal text.
The difficulty is, as soon as the customer goes to checkout - they are then able to change their delivery and billing address, thus rendering the form null and void.
My initial thought was to simply hide the customer billing and delivery information from the checkout using CSS. However, I'm unable to do this because Shopify no longer grant access to the style sheet.
Does anyone know of a way around this?

Purchasing item without registering as a user

I have this site where visitors can pay for certain digital goods, after which they'll be presented with a download link. These downloads links last for a week before they die and become useless
I want to allow users to purchase items without having to create an account first, but just by supplying the payment details and email. I figured I could send the download link to their email once paid, but this is kind of problematic if they accidentally specific an incorrect email when paying.
Any suggestions on how best to accomplish this?
I've made such a purchase on a site called WrapBootstrap (https://wrapbootstrap.com/theme/flatboard-angularjs-admin-frontend-WB0G434G7). It integrates with PayPal in that they are navigated to PayPal, pay, and when they return, PayPal notified the site the payment was successful and then WrapBootstrap displays the download link.
I liked how seamless it was but what I found was if I ever wanted to download an item again, I didn't have a personal record of it (either in email or account). One drawback from a non-account perspective. Check it out and let me know if that answers your question.

Resources