-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Supporter CPT #149
Comments
Hey This has been added to staging. I have it ready to go into production along with #152 Also can confirm that just doing the export from ACF/SCF works for the post type and meta fields. Plus the WP export works fine for the post content too (i did this to test on my local) If you would like me to importer those too, let me know :) |
@ajolo2ky Can you please review the latest update and let us know how you'd like us to proceed? |
Thanks! Yes, please import the ones that are already there. |
I will try and hop on the computer and get them imported tonight 🙂 |
Didnt get a chance last night, but have imported them today. |
This has all been imported, can we close this out now? |
@ajolo2ky Can you please confirm? |
Hi, sorry for the delay. This is worked, but the slug of supporters appears to be /blog/supporter/[supporter], it should be /supporter/[supporter] without /blog. Is that feasible? thanks. |
@ajolo2ky Let us know your thoughts on the above when you can! Thank you so much! |
Hi, sorry for the delay. I'm not finding the advanced settings box you are showing in the screenshot, where should that be inside of ACF? Thanks, |
Hi @ajolo2ky, Apologies for not being clearer earlier! The setting you're looking for is located under I haven't made any changes to it since you currently have over 830 posts relying on that permalink structure (sorry for not checking this sooner). If we want supporters to have URLs that exclude the |
Yes, we don't want to mess the current permalink structure. Can we remove the individual pages created by this CPT? I think that'd be faster. |
Is the aim for the supporters only to be shown on a single page? if so we can remove the ability for supporters to have a |
If we could have /supporter/ (instead of /blog/supporter), I'd prefer that. Having the unique URI for each supporter may have it's advantages. But if it's too problematic, for the time being I prefer just removing individual pages, just have them in /ai/endorsements and close this issue. |
Sorry not forgotten about this, im suddenly swamped with lots of issues and struggling getting through them. Will reply for pr162 on there directly |
#192 has now gone up and I have changed the permalinks (as above). Suspsect we can close this out now. |
@ajolo2ky Please confirm if we can consider this issue resolved. Thanks! |
we get an error when trying to submit the form:
[image: image.png]
…On Tue, Jan 21, 2025 at 6:13 PM Nabaht ***@***.***> wrote:
@ajolo2ky <https://github.com/ajolo2ky> Please confirm if we can consider
this issue resolved. Thanks!
—
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKJJAASBJTFAVIPJH2O6GT2LZ52BAVCNFSM6AAAAABSAQIEI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBVGMYDKMJSGE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sorry you are having issues, ive copied the {
"contact_form_id": 24780,
"status": "mail_failed",
"message": "There was an error trying to send your message. Please try again later.",
"posted_data_hash": "<REMOVED>",
"into": "<REMOVED>",
"invalid_fields": []
} I removed the custom code that was uploaded to handle form submissions and i am still getting the same issue (locally) {
"contact_form_id": 24780,
"status": "mail_failed",
"message": "There was an error trying to send your message. Please try again later.",
"posted_data_hash": "<REMOVED>",
"into": "<REMOVED>",
"invalid_fields": []
} However it seems the mail was sent Just so im not trying to compare apples to oranges, do you mind telling me what page the form is on? |
I'm testing on this page: https://opensource.org/ai/endorsements
the issue happens with Firefox but not always on Firefox Private... this
may have something to do with ublock origin or something like that.
…On Wed, Jan 22, 2025 at 10:21 AM Glynn Quelch ***@***.***> wrote:
@smaffulli <https://github.com/smaffulli>
Sorry you are having issues, ive copied the OSAID Endorsement contact
form to my local version and im also getting issues on that form locally
{
"contact_form_id": 24780,
"status": "mail_failed",
"message": "There was an error trying to send your message. Please try again later.",
"posted_data_hash": "<REMOVED>",
"into": "<REMOVED>",
"invalid_fields": []
}
I removed the custom code that was uploaded to handle form submissions and
i am still getting the same issue (locally)
{
"contact_form_id": 24780,
"status": "mail_failed",
"message": "There was an error trying to send your message. Please try again later.",
"posted_data_hash": "<REMOVED>",
"into": "<REMOVED>",
"invalid_fields": []
}
However it seems the mail was sent
image.png (view on web)
<https://github.com/user-attachments/assets/1d872dc5-8aa9-4365-8ab1-7bc4d7d9ab4b>
Just so im not trying to compare apples to oranges, do you mind telling me
what page the form is on?
—
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKJJABLT2RCEB3MY3QTZOL2L5PIRAVCNFSM6AAAAABSAQIEI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBWGY4TIMBRGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Strange, i just submitted several submissions with different browsers and tried with ublock on or off. CHROME (Regular) Without {
"contact_form_id": 71702,
"status": "mail_sent",
"message": "Thank you for your message. It has been sent.",
"posted_data_hash": "....",
"into": "#wpcf7....",
"invalid_fields": []
} With {
"contact_form_id": 71702,
"status": "mail_sent",
"message": "Thank you for your message. It has been sent.",
"posted_data_hash": "....",
"into": "#wpcf7-...",
"invalid_fields": []
} FIREFOX (Regular) {
"contact_form_id":71702,
"status":"mail_sent",
"message":"Thank you for your message. It has been sent.",
"posted_data_hash":"....",
"into":"#wpcf7-....",
"invalid_fields":[]
} You don't have a pi hole or anything else running which could stop calls, do you? (Tests from a linux machine) |
No, nothing. i'm not on a vpn or other filter.
We're receiving comments from users who have issues though, it's not just
me.
…On Wed, Jan 22, 2025 at 10:42 AM Glynn Quelch ***@***.***> wrote:
Strange, i just submitted several submissions with different browsers and
tried with ublock on or off.
*CHROME (Regular)*
Without
{
"contact_form_id": 71702,
"status": "mail_sent",
"message": "Thank you for your message. It has been sent.",
"posted_data_hash": "....",
"into": "#wpcf7....",
"invalid_fields": []
}
With
{
"contact_form_id": 71702,
"status": "mail_sent",
"message": "Thank you for your message. It has been sent.",
"posted_data_hash": "....",
"into": "#wpcf7-...",
"invalid_fields": []
}
*FIREFOX (Regular)*
{
"contact_form_id":71702,
"status":"mail_sent",
"message":"Thank you for your message. It has been sent.",
"posted_data_hash":"....",
"into":"#wpcf7-....",
"invalid_fields":[]
}
You don't have a pi hole or anything else running which could stop calls,
do you?
(Tests from a linux machine)
—
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKJJAGPVFJCL3VKCEVB6O32L5RXZAVCNFSM6AAAAABSAQIEI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBWG42DEMRUG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
it is a strange one. Do you want to open a new ticket for this, as it's not related to the supporter post type. I just need to run some errands and I will look around online and see if anyone else is reporting this when I'm back. |
I thought the issues were related. It's fine, we'll investigate this
further and open a separate ticket
…On Wed, Jan 22, 2025 at 11:19 AM Glynn Quelch ***@***.***> wrote:
it is a strange one.
Do you want to open a new ticket for this, as it's not related to the
supporter post type.
I just need to run some errands and I will look around online and see if
anyone else is reporting this when I'm back.
—
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKJJADATZ7GQPCQWMDEP232L5WCXAVCNFSM6AAAAABSAQIEI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBWHAZTGMJSGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Description
This request is to replicate the "Supporter" Custom Post Type (CPT) functionality from staging to production.
Ariel has tested the following code on the staging environment:
Ariel has requested us to move this functionality to production and ensure it is safe to deploy without breaking existing functionality.
Context
See ZD link on the internal dev request.
The text was updated successfully, but these errors were encountered: