Indy Dave

Hello! Love the new features of the editor. We would love to be able to center the table feature.

That is a feature we would employ :) My work around (in V4) is to go through creating a spreadsheet, export as a .jpg, and then post the .jpg of the data - which i can center. that process is a bit involved, but OK for something that isn't updated often. But it's unworkable for something (event lists, sign ups, donor lists) that needs to be updated often, and with that many steps, isn't something any of my mod team wants to take on. I do want to give 👍 thumbs up 👍 on the improvements to the the editor in general over V4. Well Done!

my concern was diluting this thread on invalid CSRF Cert showing as invalid. No need to respond

Heading 1 Heading 3 Heading 3 All good things come to those who wait and plan ahead Is there a way to center the table?

Thanks - just what I'm looking for 👍

Is there a replacement beta/test/play area?

Since this issue now seems to no longer be CSRF cert invalid, I'll move on. If we continue to have the risky site warnings, I'll start a fresh topic. Thanks again!

Thanks for all the help. To review . . . Here's what we've done on our end, and we still have the phishing warning, across browsers: We've disabled ALL third party applications and or plug ins Deleted systems cache Taken site off line, and put it back on line deleted browser cache and histories (on multiple admin's user machines) We're still getting the deceptive site warnings/phishing attempts detected. We have reported to google several times already.

re-reported to google. I separately re-enabled each addon, logging out and closing browser and re logged in after doing this for each (of our 4 add ons). I've also cleared history. I no longer the the CSRF cert warning, but still get the phishing warning. So in that regard, we're back one step (the cert warnings started a few days after the phishing warnings began). So with the add ons enabled, currently no cert warning, but still a phishing warning. If the pattern repeats, perhaps the cert warning will return shortly. Or not. Marc - I'm not sure which add on you're referencing? I'm not able to identify one of them as causing an issue through this process. Am I missing something?

Miss_B: Disabled adds ons, I still get the phishing warning, but no longer the next red warning page with the CSRF warning. Marc - That's correct.

Just poking around - I note when I visit our first plug in vender - their site also listed as unsecure . . that's not causing the issue is it?

Thanks for the prompt replies: Marc - I have reported to Google , and then later, that's when I started getting the CSRF error page (before we would just get the 'unsafe site' page). So my initial thought was, since we started getting the CSRF warning after I made the report, that they [google] did a deeper dive. But on second look, the CSRF warning is coming from inside the house 🤣. Miss_B: Logs are empty. I'm not aware of any changes or add ons we've made to the site recently. Admittedly, I'm the new guy. I've been onboarding for a little while, I'm not aware of any changes we've made to the board in the last 3-4weeks (apart from formatting type stuff). Add ons - Sure, we'll give that a try late this morning (we have another onboarding session, so there may be a teachable moment there for me). FWIW: This is for our Dev site if I failed to mention that previously. This is the second warning page we get [uploaded below], after the initial red warning page, is purporting that there's been phishing attempts. And these two issues (CSRF cert warning and phishing attempt warning) likely to be related or separate issues? NOTE: When this issue first raised its head last Friday, we were 'screen sharing' through The Google, and our assumption was that it was detecting that and throwing up the warnings. The CSRF and phishing warnings showed up on Monday or Tuesday of this week. Before that, it was just the GO BACK GO BACK initial red screen I shared in my first post. Thanks again. And - as a side note - this upgraded editor is slick 👍

Hi there, I'm having the the same issue on our development board since at least last Friday. We ignored it at first - and reported to google the we thought the error was... in error. 🙃 Now we get 1) can push through this page . . and arrive here . . Happy to start a new thread - wanted to check here first. Thanks - Dave 'the new guy'