LibertyTalk FM

Same problem, regardless of active theme, login status, and all plugins deactivated except for WooCommerce.

WordPress Version: 3.6.1
WooCommerce Version: 2.0.19

Right on, thank you for the quick response, and I did update the theme about 10 minutes after the first post in hopes that it might fix the problem.

Since this is the Free version, is that also why the WooDojo Widget will not save if placed on product pages?

BTW, love this theme, it is by far the best free ecommerce theme I have ever had the pleasure to use.

Finally, is there any documentation for the process of upgrading from free to premium and will the settings transition over from free to premium?

Same issue on new 3.5.1 install, timezone configured as Eastern in WP Settings.

ISSUE: Project automatically subtracts 1 day from “due-date”, i.e. if due date is 06/07/2013, upon save, plugin makes due-date 06/06/2013

My apologies, just found the behavior strange and was wondering if such an ability, i.e. “phone home” was even possible.

Was really just hoping for some feedback/conversation, not support.

Hello, really enjoy the Events Calendar Plugin, really helps elevates WordPress’ credibility in the eyes of some of the Drupal snd Joomla snobs. ??

Anywho, and if this feature is available in the Pro version forgive me as I did not see the topic in the WordPress Support forum.

FEATURE REQUEST

1.) Show Day of Week, in Widget output.

2.) Live Preview of Widget output as an Option <tab> under plugin settings.

I am not too concerned over Chrome, and it mas just more of an FYI, for anyone ion the future searching for a solution.

Thank you so much for your help, it is very much appreciated.

Update: the fix offered works in both FireFox 18.0.2 and Internet Explorer 9.0.8..

…but does not seem to work in Chrome 24.0.1312.57

Awesome thank you so much, the PDF’s are now inheriting the correct Document Properties set in Acrobat.

actionPackedAndy:

Thank you for the tip, your solution worked perfectly.

Hi Andrew, thanks, but as the message above says, their registration system is still down, which led me to posting here.

Could you by chance use your Moderator Goodness to alter the title of this post to:
[Theme: Responsive] Footer Width on Small Screen/Mobile

Danke

I tried the email link today and am still receiving the “bonk”

Also tried to re-register, but it says my email is already registered.

[SOLVED] Found and removed the echo in HOME.php

Holy Flying Spaghetti Monster, i just figured it out DAMN IT!!

This is the second time a script would not work….

Okay, the original site we registered for a client’s potential project was:

theloupe.tv registered and hosted by GoDaddy (dedicated linux PHP 4.1)

While their project never received the green light we kept the GoDaddy account and hosted our own blogs on the server.

Earlier when we were setting up “The Smoking Argus” our theme makes use of the “tomThumb_Image_Resizer”.

Whenever we plugged in the URL to the custom field, the image would not show.

Finally just putzing around it occurred to me to try the URL

theloupe.tv/smargus/images/sample.jpg and bingo it worked

Same thing here:

While smargus.com with a feed hard coded as SmArgus.com/?feed=rss2 would not work, changing the feed to:

theloupe.tv/smargus/?feed=rss2 does.

WTF

Any clue as to why this would be the case?

I am speaking of having the feed parsed through the CommentLuv reader it keeps telling me the XML document is invalid which makes me think that the feed has formatting issues within the itself.

Which is bothering me immensely.

UPDATE: Grumble grumble, my other domain on the same server political-soapbox.com (WP 2.5.1 – mysql db 4.1) works fine, even after reburning the FeedBurner feed.

However completely wiping out the smargus directory on the server uploading a zipped fresh version of WP 2.5.1 (mysql db 4.1) smargus.com still delivers the same XML error.

It is beyond my expertise, and even though a search for this problem will show multiple people having this problem, no solution has been given.

One individual suggested that it might be .htaccess, however all the solutions tried have failed to remedy the error.

Where are the experts????? Solving this problem will heap gobs and gobs of cool points for them to put on their resume.

I must now return to thinking it is somehow related to my host GoDaddy.