Sure. Instead of checking status of tickets and tasks on multiple platforms (WP org, website, email), we use @clickup as the single source of truth for all tasks we do, including development tasks and support tickets. There are some automations to automatically add new tasks to Clickup once new tickets are raised in each platform.
Before working on a ticket, we check and change the status of the related task on Clickup. Same for dev tasks. If a ticket is reopened by the customer, we will see it in the tickets list and then we update the status of that task on Clickup when starting to work on the reply.
I do review tickets and live chat conversations from our support representative but only after the conversation has taken place. I want them to have as much autonomy as possible, and by reviewing it afterwards I can comment on things that can be improved for the next time they encounter a similar situation.
I had the same feeling about one year ago and decided to ditch client work completely and focus 100% of my attention on @FluidCheckout.
Luckily I only had very few clients so it was not too difficult, making the decision was the most difficult part as income got ~70% down. Now income is getting to the same leves as before with potential to keep increasing for a long time and I’m loving the work that I do.
I could not have done it without the support of my wife, so if you are feeling this way I would say to evaluate the financial impact of that decision and the potential of your project, talk to your family and get them onboard, and define a strategy to move towards your goal. Swiftly or slowly, keep moving towards your goal.
Hey Phil, take a look at our @FluidCheckout for a better WooCommerce checkout, it is based on the shortcodes hence compatible with lots of other plugins.
I would be interested to know what types of customizations you need and if they are from a merchant or developer point of view.
Things are a lot more complex than they seem to be 🤷♂️
Basically, we listen to `click`, `keydown`, and `change` events at a global level and check the quantity fields comparing the field values with a copy of the original value set to an attribute on the same field.
The code has been redacted for brevity:
https://t.co/5uxKSzlOkI
@PoeHaH Or when decimal calculations don’t match reality (that is on JS though). We have a solution for most of these issues implemented on @FluidCheckout PRO. I can share it later when I’m on my computer. ✌️
We build @FluidCheckout, which is a replacement for the classic WooCommerce shortcode-based checkout, and has many advantages over the newer block-based checkout. One prominent advantage is more compatibility with existing 3rd-party plugins.
The main reason to replace the `select2` component is because it does not work well with the way Fluid Checkout needs to work, and we cannot easily make changes to the `select2/selectWoo` script without actually replacing it with a modified copy.
I'm seriously considering to replace the `select2/selectWoo` component on the WooCommerce checkout page with a similar component, or plain vanillaJS, to avoid all the complex issues while providing the same or better dropdown field experience.
Any objections?
@DerekAshauer@KatieKeithBarn2@SunPhotoCart Same for me with @FluidCheckout, but let me just say that the other day I found code that is 6 years old and I have been working full time on the project for at least a year now. 🙈🤣
We use @clickup to manage tasks for @FluidCheckout.
We have lists to separate sprints and backlogs for each project, but could easily use a folders too.
- current sprint
- next sprint
- backlog (general)
- backlog feature x
- backlog feature y
- support tickets
- marketing
- …
I’ve tried many PM tools over the years in different types of projects and @clickup works the best in my opinion.
Do you have any specific question, @KatieKeithBarn2?
@vikasprogrammer Finishing up new billing address positioning options for @FluidCheckout, will release this new feature in a couple of days max.
https://t.co/dh4YJyvaVz
@PoeHaH From a little background on converting websites for accessibility compliance, it is best to describing the image to help the user understand what is is about, but sometimes you need to also consider the context in which is is being used. WCAG guidelines:
https://t.co/2ZkZC1fP9S
@rilwis True. @FluidCheckout detects which other plugins are active and only load the compat files for those plugins. Same for CSS files to load only on the specific pages to avoid bloat.
In our case it is rare that a checkbox is needed, but there is an integrations tab for those.
@KatieKeithBarn2 While it is easy to start investing, remember that capital is at risk. Check the historic performance of their portfolio, not just the average or last year’s gains. Since we cannot lose the money we hold in the account, we decided not to invest for now.
@PoeHaH Same. I use that all the time, except that there is an explanation for why we are exiting the function, and for loop statements I use "// Skip ..." instead. Bail and skip statements are always one-liners ✌️