Clarityflow CMS questions
Hey sir -
It seems our articles and assets folder is the source of all of the git conflicts, every time we push to production. I have to SSH to resolve it almost every time.
the main culprit are the images we put in articles. Always git conflicts in the yml for these images.
I'm wondering if it would make sense to add some folders to gitignore. Do you see any potential issues with this?
Here's what I'm thinking should be ignored:
public/assets/article-images (this is where we're storing article images)
content/collections/articles
content/collections/blog-categories
content/collections/blog-tags
content/collections/blogs
content/collections/categories
content/collections/tags
It seems our articles and assets folder is the source of all of the git conflicts, every time we push to production. I have to SSH to resolve it almost every time.
the main culprit are the images we put in articles. Always git conflicts in the yml for these images.
I'm wondering if it would make sense to add some folders to gitignore. Do you see any potential issues with this?
Here's what I'm thinking should be ignored:
public/assets/article-images (this is where we're storing article images)
content/collections/articles
content/collections/blog-categories
content/collections/blog-tags
content/collections/blogs
content/collections/categories
content/collections/tags
Hey Jason,
With the caching, is there a way to completely prevent caching on a specific page URL?
I'm setting up these pages:
/demo
/demo/step-1
/demo/step-2
/demo/step-3
All of these have forms on them. I'm noticing I need to clear cache every time I'm doing a test submission, otherwise parts (or all) of the form is hidden.
I have the form code wrapped in {{ nocache }} but that doesn't seem to do anything.
With the caching, is there a way to completely prevent caching on a specific page URL?
I'm setting up these pages:
/demo
/demo/step-1
/demo/step-2
/demo/step-3
All of these have forms on them. I'm noticing I need to clear cache every time I'm doing a test submission, otherwise parts (or all) of the form is hidden.
I have the form code wrapped in {{ nocache }} but that doesn't seem to do anything.
Quick Q: Can you remind me, how often does the cache on statamic refresh itself? I know I can manually refresh it, but does it auto-refresh on a daily basis or something?
Hey Jason -- Today I'm running into deployment issues again on Clarityflow production. I was trying to push a small change in the footer and pricing page (we're launching our mobile apps). Divergent branch issues.
Here's what I'm seeing in the failed forge deployment: https://share.cleanshot.com/F4Xf2s1M
A) Can you quick fix this so that I can deploy these changes?
B) Can you give me step-by-step instructions on how to fix this issue myself in the future?
Thanks!
Here's what I'm seeing in the failed forge deployment: https://share.cleanshot.com/F4Xf2s1M
A) Can you quick fix this so that I can deploy these changes?
B) Can you give me step-by-step instructions on how to fix this issue myself in the future?
Thanks!
Hey sir --
Forgot if you told me this already-- Is there a way for us to manually refresh the cache on a single page, or the entire site?
My assistant set up and published an article yesterday, and we had to make a change to an image path. I can see the fix worked in the "Live Preview" in statamic, but I don't see a way to refresh the version shown on the public site.
Ideally, there would be a button somewhere in Statamic, not in Forge, so that it's easy for my assistant to refresh herself without my help.
Forgot if you told me this already-- Is there a way for us to manually refresh the cache on a single page, or the entire site?
My assistant set up and published an article yesterday, and we had to make a change to an image path. I can see the fix worked in the "Live Preview" in statamic, but I don't see a way to refresh the version shown on the public site.
Ideally, there would be a button somewhere in Statamic, not in Forge, so that it's easy for my assistant to refresh herself without my help.
Hey Jason - Can you look into this?
A person just reported that they tried to schedule a demo (I assume she meant she tried to submit our contact form at `/contact`) and it responded "Sorry, but you look like a robot."
This might be related to the reCAPTCHA add-on I installed (about a week ago, before your cache updates). Before I installed it, I was seeing a lot of spam submissions on the contact form. But I'm now realizing, this might have stopped all submissions since May 10th!
When I send a test submission, it goes through just fine. However, I noticed that it's not showing the "success" message after submission like it did when I implemented it a couple weeks ago (maybe the caching update impacted this?).
Could you look into:
A person just reported that they tried to schedule a demo (I assume she meant she tried to submit our contact form at `/contact`) and it responded "Sorry, but you look like a robot."
This might be related to the reCAPTCHA add-on I installed (about a week ago, before your cache updates). Before I installed it, I was seeing a lot of spam submissions on the contact form. But I'm now realizing, this might have stopped all submissions since May 10th!
When I send a test submission, it goes through just fine. However, I noticed that it's not showing the "success" message after submission like it did when I implemented it a couple weeks ago (maybe the caching update impacted this?).
Could you look into:
- Test the contact form on different browsers, and see if your submissions are blocked... And what might be causing others' to be blocked?
- I'm not aware of the "Sorry, but you look like a robot." response message. Maybe that's something from Google's recaptcha service? Do you know where that's being set or triggered?
- Ensure the success message after submission is shown
Thanks!
Hey - I'm wondering what we can do to speed up the site overall? I've been noticing it's a bit sluggish on a fresh page load. And ahrefs is flagging most pages as slow loading.
Do you think increasing the droplet size would help? We're currently on the cheapest level: 512MB memory, 0.5TB transfer. (costs almost nothing). I'm thinking up it to: Basic, Regular Intel, 2GB Memory, 3TB transfer. $18/month. Might be overkill, but it's still pretty cheap.
Is that that move? Any other ideas?
If increasing droplet size, it says I have to turn off our droplet for the upgrade. I assume that means a brief downtime. Is it just a matter of turning it off, upgrading, then turning back on, and only down for a few minutes? (I'm not very familiar with DO).
Do you think increasing the droplet size would help? We're currently on the cheapest level: 512MB memory, 0.5TB transfer. (costs almost nothing). I'm thinking up it to: Basic, Regular Intel, 2GB Memory, 3TB transfer. $18/month. Might be overkill, but it's still pretty cheap.
Is that that move? Any other ideas?
If increasing droplet size, it says I have to turn off our droplet for the upgrade. I assume that means a brief downtime. Is it just a matter of turning it off, upgrading, then turning back on, and only down for a few minutes? (I'm not very familiar with DO).
Do you know how we make staging.clarityflow.com invisible to the public (and from search engines)?
I'm thinking something like: If I'm logged in at staging.clarityflow.com/cp then everything is visible to me, otherwise block access.
Or set a password on the server level?
I still want to have the current syncing from main to staging in place, if possible.
I'm thinking something like: If I'm logged in at staging.clarityflow.com/cp then everything is visible to me, otherwise block access.
Or set a password on the server level?
I still want to have the current syncing from main to staging in place, if possible.
