H5K

5 hours ago, Marc Stridgen said:

If its only just started to work, its very likely your sitemap hasnt fully built up as of yet

Well it's been over 24 hours now and the site map is still very very incomplete.

19 minutes ago, Jim M said:

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. 

 

12 minutes ago, Jim M said:

Please ensure that CloudFlare protection stays off for our investigation.

Done. It is the site in my client area with "-" in the domain name. Thank you very much.

Edit: Erm.. it doesn't seem to be erroring anymore, but the sitemap seems to be incomplete. Our pages (especially download page) should appear in the site map but do not seem to be. Could just take a quick look at it? Thanks.

3 hours ago, Jim M said:

Please note that LiteSpeed is not supported by our software.

 

I would not use that query string as a test as it is something we use on the page and will correctly be empty with that value. Everything seems fine from an access point of view.

 

Please note that you are also using CloudFlare with DDoS protection on so that may be stopping your server from seeing the page exists.

I tried again (now after re-uploading all files) completely disabling Cloudflare and switching back to Apache instead of Litespeed and the issue is persisting.

I've also checked the System Error Logs and Error Logs and I'm not seeing anything that seems to be related. I am not sure what else to try. Is there a way to escalate this? I don't mind sharing my community login info or FTP info.

Just tried uploading all original files again -- unfortunately the issue persists.

6 minutes ago, Jim M said:

I am getting error too many redirects from your server, you will want to check your server configuration and remove any custom redirects or rewrites. 

sorry, fixed that

sitemap.php is loading now

however sitemap.php?testsettings=1   is not

Things I've tried:

• Switching from LiteSpeed back to Apache
• Renaming the ".htaccess" in the root directory
• Support -> Something isn't working correctly
• Disabling CSF/LFD

20 minutes ago, Jim M said:

Is the sitemap.php file present in your root directory?

Yes, it is. https://dekaron-rising.com/sitemap.php

That said, I found something interesting in the error logs.

sitemap.php works

sitemap.php?testsettings=1 does not

Edit: Now neither seem to be working.

This is the content of sitemap.php

<?php
/**
 * @brief        Public sitemap gateway file
 * @author        <a href='https://www.invisioncommunity.com'>Invision Power Services, Inc.</a>
 * @copyright    (c) Invision Power Services, Inc.
 * @license       https://www.invisioncommunity.com/legal/standards/
 * @package        Invision Community
 * @since        18 Feb 2013
 */

/**
 * Path to your IP.Board directory with a trailing /
 * Leave blank if you have not moved sitemap.php
 */
\define('REPORT_EXCEPTIONS', TRUE);
$_SERVER['SCRIPT_FILENAME']    = __FILE__;
$path    = '';

$_GET['app']        = 'core';
$_GET['module']        = 'sitemap';
$_GET['controller']    = 'sitemap';

require_once $path . 'init.php';

if ( \IPS\Request::i()->testsettings )
{
    exit;
}

\IPS\Dispatcher\External::i()->run();

1 hour ago, Jim M said:

Your community has quite a few issues going on right now.

1. It has an invalid SSL certificate.
2. The URL you included there has www, whereas your community does not use www.
3. Looks like you're using a CDN on your community and it is not allowing things to load for me due to a CORs policy you're setting.

Items 1 and 2 may really be causing the issue here as the software isn't detecting the right/valid URL or may not entirely be able to get to it.

Thanks for looking into it:

1. This was occurring because I was changing some settings to troubleshoot. I changed them back.

2. I tried both with and without

Unfortunately even without the SSL errors I get the same error with/without www.

Our sitemap is missing quite a few links.

We're trying to switch it back to "use recommended settings" to see if that fixes it but it's saying the URL is invalid, even though I have verified that the file exists and has 0644 permissions.

We're on the latest version of IPS too.

Update:

Followed these steps which worked like a charm.

This happened after switching the theme storage settings to our S3.

Our entire site is down and we can't access the admin CP to switch it back or clear system cache.

And I guess we can't create a support ticket because we're self hosted.

[[Template core/admin/global/globalTemplate is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

On 10/5/2023 at 10:22 PM, David8888 said:

Hi there,

Invision Community doesn't use stripe subscriptions and its very annoying for me personally since we primarily use it for our site and its were most of our income comes from. There so many customers and if it were to use the Stripe Subscription System it would be much easier. 

I think subscriptions are managed because subscriptions is because Commerce facilitates the renewal process and created “invoices”. For our use case this is actually a good thing since because the invoices are tied to fields and information we need that can’t (or couldn’t) easily be created on the Stripe side (though that could have changed). 
 

I think if Stripe managed the subscriptions and renewals IPS would have to call the Stripe API and pull data in order to synchronize invoices. Could be wrong though. 

Internal embeds and video attachments do not have the same customization options as images.

Images can be.....

• Put on a bullet
• Aligned to the right
  • 

• Resized  
  Resized 

Suggestions for IPS Embed (Topics, Articles, Gallery items, etc) Customization Options

• Suggestions
  • Allow it to be put under a bullet point
  • Allow it to be resized
  • Allow alignment to be customizable

Suggestions Video Attachment Embed Customization Options

• Allow the same options as allowed for images..

Bump

Agree with OP.

From a developer perspective I fail to see how the support/ticket system is causing enough overhead for the IPS team to warrant it being decommissioned. Just sounds ridiculous considering it's so similar to forum/pages functionality.

"Oh there's already other ticket platforms" is an irrelevant statement. Obviously there's alternatives, but it's inconvenient and integration is not usually fun. The ticket system can be tied to purchases, it makes sense to be part of the same platform.

On 9/6/2023 at 8:20 AM, Marc Stridgen said:

This is not something that will be returning within the platform, and is not actually part of the v5 product. As mentioned in many areas, we will be concentrating more on the community side of things. There are many support products out there that people can choose to use if required. Even simplifying it, as you put it, would be time in developing a part of the product we no longer wish to continue with as a company

Wow, what an inconsiderate and tone deaf response to a loyal client that has been with IPS for 20+ years. You realize the category this thread was posted in is called "Feedback", right?

On 8/18/2023 at 1:21 AM, bing11 said:

I don't think it is good idea  do this.

Apple and google never think about  to close apple store and  google play.

 

Marketplace is not making money or it is making more job . But It can make me go to this site everyday.

 

Yeah, because Apple and Google know the value of creating a  "platform" and empowering developers.

[ ~]# locale -a
aa_DJ
aa_DJ.iso88591
aa_DJ.utf8
aa_ER
aa_ER@saaho
aa_ER.utf8
aa_ER.utf8@saaho
aa_ET
aa_ET.utf8
af_ZA
af_ZA.iso88591
af_ZA.utf8
agr_PE
agr_PE.utf8
ak_GH
ak_GH.utf8
am_ET
am_ET.utf8
an_ES
an_ES.iso885915
an_ES.utf8
anp_IN
anp_IN.utf8
ar_AE
ar_AE.iso88596
ar_AE.utf8
ar_BH
ar_BH.iso88596
ar_BH.utf8
ar_DZ
ar_DZ.iso88596
ar_DZ.utf8
ar_EG
ar_EG.iso88596
ar_EG.utf8
ar_IN
ar_IN.utf8
ar_IQ
ar_IQ.iso88596
ar_IQ.utf8
ar_JO
ar_JO.iso88596
ar_JO.utf8
ar_KW
ar_KW.iso88596
ar_KW.utf8
ar_LB
ar_LB.iso88596
ar_LB.utf8
ar_LY
ar_LY.iso88596
ar_LY.utf8
ar_MA
ar_MA.iso88596
ar_MA.utf8
ar_OM
ar_OM.iso88596
ar_OM.utf8
ar_QA
ar_QA.iso88596
ar_QA.utf8
ar_SA
ar_SA.iso88596
ar_SA.utf8
ar_SD
ar_SD.iso88596
ar_SD.utf8
ar_SS
ar_SS.utf8
ar_SY
ar_SY.iso88596
ar_SY.utf8
ar_TN
ar_TN.iso88596
ar_TN.utf8
ar_YE
ar_YE.iso88596
ar_YE.utf8
as_IN
as_IN.utf8
ast_ES
ast_ES.iso885915
ast_ES.utf8
ayc_PE
ayc_PE.utf8
az_AZ
az_AZ.utf8
az_IR
az_IR.utf8
be_BY
be_BY.cp1251
be_BY@latin
be_BY.utf8
be_BY.utf8@latin
bem_ZM
bem_ZM.utf8
ber_DZ
ber_DZ.utf8
ber_MA
ber_MA.utf8
bg_BG
bg_BG.cp1251
bg_BG.utf8
bhb_IN.utf8
bho_IN
bho_IN.utf8
bho_NP
bho_NP.utf8
bi_VU
bi_VU.utf8
bn_BD
bn_BD.utf8
bn_IN
bn_IN.utf8
bo_CN
bo_CN.utf8
bo_IN
bo_IN.utf8
bokmal
br_FR
br_FR@euro
br_FR.iso88591
br_FR.iso885915@euro
br_FR.utf8
brx_IN
brx_IN.utf8
bs_BA
bs_BA.iso88592
bs_BA.utf8
byn_ER
byn_ER.utf8
C
ca_AD
ca_AD.iso885915
ca_AD.utf8
ca_ES
ca_ES@euro
ca_ES.iso88591
ca_ES.iso885915@euro
ca_ES.utf8
ca_ES.utf8@valencia
ca_ES@valencia
ca_FR
ca_FR.iso885915
ca_FR.utf8
ca_IT
ca_IT.iso885915
ca_IT.utf8
catalan
ce_RU
ce_RU.utf8
chr_US
chr_US.utf8
cmn_TW
cmn_TW.utf8
crh_UA
crh_UA.utf8
croatian
csb_PL
csb_PL.utf8
cs_CZ
cs_CZ.iso88592
cs_CZ.utf8
C.utf8
cv_RU
cv_RU.utf8
cy_GB
cy_GB.iso885914
cy_GB.utf8
czech
da_DK
da_DK.iso88591
da_DK.iso885915
da_DK.utf8
danish
dansk
de_AT
de_AT@euro
de_AT.iso88591
de_AT.iso885915@euro
de_AT.utf8
de_BE
de_BE@euro
de_BE.iso88591
de_BE.iso885915@euro
de_BE.utf8
de_CH
de_CH.iso88591
de_CH.utf8
de_DE
de_DE@euro
de_DE.iso88591
de_DE.iso885915@euro
de_DE.utf8
de_IT
de_IT.iso88591
de_IT.utf8
de_LI.utf8
de_LU
de_LU@euro
de_LU.iso88591
de_LU.iso885915@euro
de_LU.utf8
deutsch
doi_IN
doi_IN.utf8
dsb_DE
dsb_DE.utf8
dutch
dv_MV
dv_MV.utf8
dz_BT
dz_BT.utf8
eesti
el_CY
el_CY.iso88597
el_CY.utf8
el_GR
el_GR@euro
el_GR.iso88597
el_GR.iso88597@euro
el_GR.utf8
en_AG
en_AG.utf8
en_AU
en_AU.iso88591
en_AU.utf8
en_BW
en_BW.iso88591
en_BW.utf8
en_CA
en_CA.iso88591
en_CA.utf8
en_DK
en_DK.iso88591
en_DK.utf8
en_GB
en_GB.iso88591
en_GB.iso885915
en_GB.utf8
en_HK
en_HK.iso88591
en_HK.utf8
en_IE
en_IE@euro
en_IE.iso88591
en_IE.iso885915@euro
en_IE.utf8
en_IL
en_IL.utf8
en_IN
en_IN.utf8
en_NG
en_NG.utf8
en_NZ
en_NZ.iso88591
en_NZ.utf8
en_PH
en_PH.iso88591
en_PH.utf8
en_SC.utf8
en_SG
en_SG.iso88591
en_SG.utf8
en_US
en_US@ampm
en_US.iso88591
en_US.iso885915
en_US.utf8
en_US.utf8@ampm
en_ZA
en_ZA.iso88591
en_ZA.utf8
en_ZM
en_ZM.utf8
en_ZW
en_ZW.iso88591
en_ZW.utf8
eo
eo.utf8
es_AR
es_AR.iso88591
es_AR.utf8
es_BO
es_BO.iso88591
es_BO.utf8
es_CL
es_CL.iso88591
es_CL.utf8
es_CO
es_CO.iso88591
es_CO.utf8
es_CR
es_CR.iso88591
es_CR.utf8
es_CU
es_CU.utf8
es_DO
es_DO.iso88591
es_DO.utf8
es_EC
es_EC.iso88591
es_EC.utf8
es_ES
es_ES@euro
es_ES.iso88591
es_ES.iso885915@euro
es_ES.utf8
es_GT
es_GT.iso88591
es_GT.utf8
es_HN
es_HN.iso88591
es_HN.utf8
es_MX
es_MX.iso88591
es_MX.utf8
es_NI
es_NI.iso88591
es_NI.utf8
es_PA
es_PA.iso88591
es_PA.utf8
es_PE
es_PE.iso88591
es_PE.utf8
es_PR
es_PR.iso88591
es_PR.utf8
es_PY
es_PY.iso88591
es_PY.utf8
es_SV
es_SV.iso88591
es_SV.utf8
estonian
es_US
es_US.iso88591
es_US.utf8
es_UY
es_UY.iso88591
es_UY.utf8
es_VE
es_VE.iso88591
es_VE.utf8
et_EE
et_EE.iso88591
et_EE.iso885915
et_EE.utf8
eu_ES
eu_ES@euro
eu_ES.iso88591
eu_ES.iso885915@euro
eu_ES.utf8
fa_IR
fa_IR.utf8
ff_SN
ff_SN.utf8
fi_FI
fi_FI@euro
fi_FI.iso88591
fi_FI.iso885915@euro
fi_FI.utf8
fil_PH
fil_PH.utf8
finnish
fo_FO
fo_FO.iso88591
fo_FO.utf8
fr_BE
fr_BE@euro
fr_BE.iso88591
fr_BE.iso885915@euro
fr_BE.utf8
fr_CA
fr_CA.iso88591
fr_CA.utf8
fr_CH
fr_CH.iso88591
fr_CH.utf8
french
fr_FR
fr_FR@euro
fr_FR.iso88591
fr_FR.iso885915@euro
fr_FR.utf8
fr_LU
fr_LU@euro
fr_LU.iso88591
fr_LU.iso885915@euro
fr_LU.utf8
fur_IT
fur_IT.utf8
fy_DE
fy_DE.utf8
fy_NL
fy_NL.utf8
ga_IE
ga_IE@euro
ga_IE.iso88591
ga_IE.iso885915@euro
ga_IE.utf8
galego
galician
gd_GB
gd_GB.iso885915
gd_GB.utf8
german
gez_ER
gez_ER@abegede
gez_ER.utf8
gez_ER.utf8@abegede
gez_ET
gez_ET@abegede
gez_ET.utf8
gez_ET.utf8@abegede
gl_ES
gl_ES@euro
gl_ES.iso88591
gl_ES.iso885915@euro
gl_ES.utf8
greek
gu_IN
gu_IN.utf8
gv_GB
gv_GB.iso88591
gv_GB.utf8
hak_TW
hak_TW.utf8
ha_NG
ha_NG.utf8
hebrew
he_IL
he_IL.iso88598
he_IL.utf8
hif_FJ
hif_FJ.utf8
hi_IN
hi_IN.utf8
hne_IN
hne_IN.utf8
hr_HR
hr_HR.iso88592
hr_HR.utf8
hrvatski
hsb_DE
hsb_DE.iso88592
hsb_DE.utf8
ht_HT
ht_HT.utf8
hu_HU
hu_HU.iso88592
hu_HU.utf8
hungarian
hy_AM
hy_AM.armscii8
hy_AM.utf8
ia_FR
ia_FR.utf8
icelandic
id_ID
id_ID.iso88591
id_ID.utf8
ig_NG
ig_NG.utf8
ik_CA
ik_CA.utf8
is_IS
is_IS.iso88591
is_IS.utf8
italian
it_CH
it_CH.iso88591
it_CH.utf8
it_IT
it_IT@euro
it_IT.iso88591
it_IT.iso885915@euro
it_IT.utf8
iu_CA
iu_CA.utf8
ja_JP
ja_JP.eucjp
ja_JP.ujis
ja_JP.utf8
japanese
japanese.euc
kab_DZ
kab_DZ.utf8
ka_GE
ka_GE.georgianps
ka_GE.utf8
kk_KZ
kk_KZ.pt154
kk_KZ.utf8
kl_GL
kl_GL.iso88591
kl_GL.utf8
km_KH
km_KH.utf8
kn_IN
kn_IN.utf8
kok_IN
kok_IN.utf8
ko_KR
ko_KR.euckr
ko_KR.utf8
korean
korean.euc
ks_IN
ks_IN@devanagari
ks_IN.utf8
ks_IN.utf8@devanagari
ku_TR
ku_TR.iso88599
ku_TR.utf8
kw_GB
kw_GB.iso88591
kw_GB.utf8
ky_KG
ky_KG.utf8
lb_LU
lb_LU.utf8
lg_UG
lg_UG.iso885910
lg_UG.utf8
li_BE
li_BE.utf8
lij_IT
lij_IT.utf8
li_NL
li_NL.utf8
lithuanian
ln_CD
ln_CD.utf8
lo_LA
lo_LA.utf8
lt_LT
lt_LT.iso885913
lt_LT.utf8
lv_LV
lv_LV.iso885913
lv_LV.utf8
lzh_TW
lzh_TW.utf8
mag_IN
mag_IN.utf8
mai_IN
mai_IN.utf8
mai_NP
mai_NP.utf8
mfe_MU
mfe_MU.utf8
mg_MG
mg_MG.iso885915
mg_MG.utf8
mhr_RU
mhr_RU.utf8
mi_NZ
mi_NZ.iso885913
mi_NZ.utf8
miq_NI
miq_NI.utf8
mjw_IN
mjw_IN.utf8
mk_MK
mk_MK.iso88595
mk_MK.utf8
ml_IN
ml_IN.utf8
mni_IN
mni_IN.utf8
mn_MN
mn_MN.utf8
mr_IN
mr_IN.utf8
ms_MY
ms_MY.iso88591
ms_MY.utf8
mt_MT
mt_MT.iso88593
mt_MT.utf8
my_MM
my_MM.utf8
nan_TW
nan_TW@latin
nan_TW.utf8
nan_TW.utf8@latin
nb_NO
nb_NO.iso88591
nb_NO.utf8
nds_DE
nds_DE.utf8
nds_NL
nds_NL.utf8
ne_NP
ne_NP.utf8
nhn_MX
nhn_MX.utf8
niu_NU
niu_NU.utf8
niu_NZ
niu_NZ.utf8
nl_AW
nl_AW.utf8
nl_BE
nl_BE@euro
nl_BE.iso88591
nl_BE.iso885915@euro
nl_BE.utf8
nl_NL
nl_NL@euro
nl_NL.iso88591
nl_NL.iso885915@euro
nl_NL.utf8
nn_NO
nn_NO.iso88591
nn_NO.utf8
no_NO
no_NO.ISO-8859-1
norwegian
nr_ZA
nr_ZA.utf8
nso_ZA
nso_ZA.utf8
nynorsk
oc_FR
oc_FR.iso88591
oc_FR.utf8
om_ET
om_ET.utf8
om_KE
om_KE.iso88591
om_KE.utf8
or_IN
or_IN.utf8
os_RU
os_RU.utf8
pa_IN
pa_IN.utf8
pap_AW
pap_AW.utf8
pap_CW
pap_CW.utf8
pa_PK
pa_PK.utf8
pl_PL
pl_PL.iso88592
pl_PL.utf8
polish
portuguese
POSIX
ps_AF
ps_AF.utf8
pt_BR
pt_BR.iso88591
pt_BR.utf8
pt_PT
pt_PT@euro
pt_PT.iso88591
pt_PT.iso885915@euro
pt_PT.utf8
quz_PE
quz_PE.utf8
raj_IN
raj_IN.utf8
romanian
ro_RO
ro_RO.iso88592
ro_RO.utf8
ru_RU
ru_RU.iso88595
ru_RU.koi8r
ru_RU.utf8
russian
ru_UA
ru_UA.koi8u
ru_UA.utf8
rw_RW
rw_RW.utf8
sah_RU
sah_RU.utf8
sa_IN
sa_IN.utf8
sat_IN
sat_IN.utf8
sc_IT
sc_IT.utf8
sd_IN
sd_IN@devanagari
sd_IN.utf8
sd_IN.utf8@devanagari
se_NO
se_NO.utf8
sgs_LT
sgs_LT.utf8
shn_MM
shn_MM.utf8
shs_CA
shs_CA.utf8
sid_ET
sid_ET.utf8
si_LK
si_LK.utf8
sk_SK
sk_SK.iso88592
sk_SK.utf8
slovak
slovene
slovenian
sl_SI
sl_SI.iso88592
sl_SI.utf8
sm_WS
sm_WS.utf8
so_DJ
so_DJ.iso88591
so_DJ.utf8
so_ET
so_ET.utf8
so_KE
so_KE.iso88591
so_KE.utf8
so_SO
so_SO.iso88591
so_SO.utf8
spanish
sq_AL
sq_AL.iso88591
sq_AL.utf8
sq_MK
sq_MK.utf8
sr_ME
sr_ME.utf8
sr_RS
sr_RS@latin
sr_RS.utf8
sr_RS.utf8@latin
ss_ZA
ss_ZA.utf8
st_ZA
st_ZA.iso88591
st_ZA.utf8
sv_FI
sv_FI@euro
sv_FI.iso88591
sv_FI.iso885915@euro
sv_FI.utf8
sv_SE
sv_SE.iso88591
sv_SE.iso885915
sv_SE.utf8
swedish
sw_KE
sw_KE.utf8
sw_TZ
sw_TZ.utf8
szl_PL
szl_PL.utf8
ta_IN
ta_IN.utf8
ta_LK
ta_LK.utf8
tcy_IN.utf8
te_IN
te_IN.utf8
tg_TJ
tg_TJ.koi8t
tg_TJ.utf8
thai
the_NP
the_NP.utf8
th_TH
th_TH.tis620
th_TH.utf8
ti_ER
ti_ER.utf8
ti_ET
ti_ET.utf8
tig_ER
tig_ER.utf8
tk_TM
tk_TM.utf8
tl_PH
tl_PH.iso88591
tl_PH.utf8
tn_ZA
tn_ZA.utf8
to_TO
to_TO.utf8
tpi_PG
tpi_PG.utf8
tr_CY
tr_CY.iso88599
tr_CY.utf8
tr_TR
tr_TR.iso88599
tr_TR.utf8
ts_ZA
ts_ZA.utf8
tt_RU
tt_RU@iqtelif
tt_RU.utf8
tt_RU.utf8@iqtelif
turkish
ug_CN
ug_CN.utf8
uk_UA
uk_UA.koi8u
uk_UA.utf8
unm_US
unm_US.utf8
ur_IN
ur_IN.utf8
ur_PK
ur_PK.utf8
uz_UZ
uz_UZ@cyrillic
uz_UZ.iso88591
uz_UZ.utf8
uz_UZ.utf8@cyrillic
ve_ZA
ve_ZA.utf8
vi_VN
vi_VN.utf8
wa_BE
wa_BE@euro
wa_BE.iso88591
wa_BE.iso885915@euro
wa_BE.utf8
wae_CH
wae_CH.utf8
wal_ET
wal_ET.utf8
wo_SN
wo_SN.utf8
xh_ZA
xh_ZA.iso88591
xh_ZA.utf8
yi_US
yi_US.cp1255
yi_US.utf8
yo_NG
yo_NG.utf8
yue_HK
yue_HK.utf8
yuw_PG
yuw_PG.utf8
zh_CN
zh_CN.gb18030
zh_CN.gb2312
zh_CN.gbk
zh_CN.utf8
zh_HK
zh_HK.big5hkscs
zh_HK.utf8
zh_SG
zh_SG.gb2312
zh_SG.gbk
zh_SG.utf8
zh_TW
zh_TW.big5
zh_TW.euctw
zh_TW.utf8
zu_ZA
zu_ZA.iso88591
zu_ZA.utf8

Commerce Feedback: Voiced but Unheard

Commerce is in need of some dire improvements considering it is a life-support system for many communities.

Recurring recommendations have been made for years but left unheard. While we understand that Commerce and especially payment method integration requires a lot of development, I think we can all agree on its necessity and the importance of a good customer experience.

Previous Feedback: 2018 -> 2023

• Payment Method Display:
  •  
    • 

• User Experience / Customization
  • Store front-page customization
  • Separation of currencies
    • Topic:
    •  
    • https://invisioncommunity.com/forums/topic/467574-currencies-available-for-location-not-language
• Pricing Features
• Missing Features from Existing Integrations
  •  
• QoL

________________________________________________________________________________

At the end here I'm just going to tag any staff or user that has previously shared their thoughts on topic.

•  
• @LaCollision@Richard Arch@OctoDev@SjorsK@Jordan Miller@Umaar@ZLTRGO@iozay@Ghost Face@Kirill Gromov@PatrickRQ@Nakamura RTS@ahc@PatrickRQ@The DeaDly@AlexWebsites

On 5/15/2023 at 3:49 PM, Stuart Silvester said:

There's no bug here, changing the data that the Gateway/API references is going to cause problems. That goes for any gateway if you're changing something material such as the data source or account IDs.

Does having multiple gateways of the same type also cause issues? For example, two separate Stripe accounts that are both configured to use credit cards?

59 minutes ago, Stuart Silvester said:

This issue was being caused by the payment gateway trying to use customer data from Stripe's test mode on the live gateway.

It's always a good idea remove the gateway that was used for the Stripe test mode during set up and create a new one for live transactions.

@Stuart Silvester@Jim M this seems to be a bug. I think I recall having a similar issue after editing an existing gateway and replacing the test api key/webhook/etc with the live info. Could you confirm if there is a bug with editing an existing gateway?

20 hours ago, FM Graphics said:

Thanks @H5K but that doesn't seem to be the issue.

I've checked the logs on Stripe and it seems to be related to a customer issue.

I'm getting the below message today when testing.

'No such customer: 'cus_xxxxxxxxxxxxx'; a similar object exists in test mode, but a live mode key was used to make this request.'

I selected all events on Stripe when setting up the account and as mentioned I'm in live mode with all live secrets and webhooks setup.

I can't recall specifically if this ended up being the issue or not but going to write it anyway just in case:

• I think I got a similar error when I had multiple Stripe card checkouts with different Stripe accounts

Also interested in this. I’ve noticed sometimes uploads get corrupted and the file size seems to be extremely smile. 

Make sure the Stripe IPs are whitelisted. I got that same error because my firewall was blocking some of the connections to Stripe. 

2 hours ago, Randy Calvert said:

This also goes to show as much as Google loves to preach speed and performance… it’s somewhat of a do as I say and not as I do. 

Between their ad code and analytics code… Google has a long way to go to clean up their own house. 🙂 

I like Cloudflare's tool (you have to have the domain added to your account in Cloudflare in order to run their tool).

19 hours ago, Marc Stridgen said:

That would be intended. If you change a field type, the system will notice that field type as being outside what the default is, and try to correct it

Thank you for the response and apologies for the confusion. I was not questioning whether the table modification message was intended or not.

I am questioning whether it is intended for gallery_images.image_file_size to be an int and not a bigint. The gallery has recently improved support for videos which can be considerably large. The reason we had to change the column datatype is because our users got an error when they tried to upload videos that were too large.

Hi,

Our community allows users to upload very large videos to the gallery. We recently had to change the image_file_size column datatype in the gallery_images table from INT to BIGINT to support this.

Reporting this because now we're getting a warning in the AdminCP because we changed the table. Tagging @Olivia Clark and @Andy Millne since you two seem to be very familiar with the recent gallery changes and probably can confirm if this is a bug or intended.

Thanks