jrothra
Forum Replies Created
-
After adding that code to the .htaccess file, I re-ran speed tests. Both Pingdom and GTMetrics/YSlow continue to say I need to “add expires headers.” I thought that this code was doing that.
Hmm… odd, but probably only to me since this is a bit above my head right now.
I added the info to .htaccess (which I accessed via Yoast > Tools).
When I look at the cPanel, there is an option for Apache, so I’m sure the server uses Apache, not Nginx. I have, however, asked the host via a ticket.
Here’s a screen shot of the Apache handlers section which seems to indicate that it is an Apache server.
- This reply was modified 6 years ago by jrothra.
When you go to WP-Optimize > Cache > Static file headers, what is there?
This is what I see: screen shot
Though looking at your site, it seems to be running on Nginx.
I have no idea what that is or if my site uses it. I do have an .htaccess file on the server, which does use Apache.
Forum: Plugins
In reply to: [WooCommerce] Product Search Widget Returns No ResultsIt’s not a fix, but I replaced the default WooCommerce Product Search widget with the AJAX Search for WooCommerce plugin.
Kenin,
That was the solution: the extension was set as inactive. I can’t believe I overlooked that.
Forum: Reviews
In reply to: [OceanWP] Ok theme with terrible support.When I purchased the premium bundle in 2018, the support seemed fine. However, you are right, this year it’s nosedived.
Forum: Reviews
In reply to: [OceanWP] Great Theme – Really Poor Support!!!!It’s true that for a small-staffed theme company, trying to deal with updating the theme and responding to free customer support can become overwhelming. However, I would think that paid customers would get a higher priority and not have to wait days, weeks, or months for a reply. If the theme is growing that fast, it may be worth investing into more staff to provide support. The return on that investment could be quite significant if done well.
Forum: Reviews
In reply to: [OceanWP] No Support so farI’ve experienced this same, bad support lately, too. Not only are they very slow to respond, they also fail to acknowledge any problems with their themes/plugins. I had a problem and Amit blamed third party plugins. I tested that theory by installing a fresh WordPress, installing OceanWP 1.7.3, and Ocean Extra 1.5.19. I wasn’t using any other plugin or theme and no custom CSS/JS, just WordPress and OceanWP, yet the problems remained, which meant it’s an OceanWP problem. They fail to acknowledge this.
Poor service at best, outright total disservice at worst.
Forum: Plugins
In reply to: [WooCommerce] PoD Drop Shipping and Sales Tax – I’m Paying It, Not CustomerSECOND UPDATE
I tried something, but it didn’t seem to work. I created a new tax class called “Texas only,” and set the tax rate according to what should be charged. I also told the Printful plugin to calculate sales taxes.
Next, I set the Printful PoD products to the tax class of “Standard,” and set the tax class for my digital products to “Texas only.”
Using these settings, I ran two tests:
Test 1: Activating WooCommerce Services’ automated tax rates
The results for Texas zip codes
On digital product: sales tax was charged
On Printful product: sales tax was charged
I didn’t do the math to see what rate was being charged, but in this case, taxes should be charged on both.The results for California zip codes
Same as with Texas zip codes. In this case, it should have charged taxes on the Printful, but not the digital items.Test 2: Deactivating WC Services’ automated tax rates
The results were the same as above: it charged taxes.In short, no matter what I’ve tried, I can’t get the system to let Printful calculate taxes on products it prints on demand, but for digital products, charge sales tax only to Texas customers.
Forum: Plugins
In reply to: [WooCommerce] PoD Drop Shipping and Sales Tax – I’m Paying It, Not CustomerUPDATE: I found this video: https://youtu.be/98JuvBEEBQQ?t=650 (start at 10:50)
I noticed, however, that choosing that option in Printful charges taxes for all products, including non-Printful items. This means that customers in California or North Carolina would be charged sales tax on my MP3s (digital downloads), even though I have no nexus in those states and, thus, would be collecting sales tax illegally.
How do I allow Printful to charge calculate sales tax, but for certain products (my mp3s and ebook), charge sales tax only to Texas customers based on their zip code (sales tax varies throughout Texas)?
I understand and I apologize for overreacting. All’s forgiven and good between us.
My site totally crashed (my own fault, I accidentally deleted the database files), but thanks to backups, got it back. However, I lost the staging site, so I redownloaded the plugin and created a new staging site.
Interestingly, the new staging site is operating just like the live site, which is what I would expect. Why it didn’t before is quite baffling. Anyway, I again apologize for my overreaction.
Rene,
I’m sorry you are irritated, but your dismissive condescension is unwelcome and offensive.
I am aware that Font Awesome are icons and that the example I show in the video is a form field. However, what is displayed in that checkbox is a Font Awesome icon.
The theme (OceanWP) recently added full Font Awesome 5 compatibility to fix this problem. However, it did not fix it on my live site, so I decided to create a staged clone using your plugin to try to figure out why. However, I discovered that the staged version worked while the live didn’t.
I made that video at that point (the two sites at that point were identical).
I didn’t want to keep my live site up with broken features, so I added custom CSS to temporarily fix the problem (a hack I shouldn’t have to do). I added the following CSS to the live site (the staged site didn’t need it):
input[type=checkbox]:checked:before { font-weight: 900; font-family: 'Font Awesome 5 Free'; }As you can see, it declares that a Font Awesome 5 icon displays, and this is what you are seeing on the live site.
Again, as I said in the original post, the staged site does not require this hack, meaning it operates differently than the live site.
To test the cache issue, I cleared the site cache and checked it on three computers, two to three browsers on each, and checked via my phone. The problem was consistent, eliminating a cache issue.
That’s why I created the video which shows the differences (screen shots wouldn’t necessarily have worked because it’s a matter of form fields being active vs. inactive).
In the video you’ll see the following:
– Begins on the live site (black admin bar)
– Moves to the footer and clicks on and off in a checkbox
– Switches to the staged site (orange admin bar)
– Moves to the same footer and clicks on and off in the same checkboxIn it you’ll see that for the live site, the activated checkmark doesn’t show up, but it does show up in the staged site (that’s the difference). This difference happens throughout the site, but I dind’t think I needed to video every instance.
Forum: Themes and Templates
In reply to: [OceanWP] OceanWP + Woocommerce: checkout issue with checkboxes