css/php nightmares
by Mark
i’ve been nearly at it the entire-freakin’-day setting up the shop outside of the main UL website. As you recall earlier, the plugin on the UL site went haywire and had to disable it by deleting the plugin via FTP. Attempts to renable the plugin have failed and the site had been stuck without a functioning cart for over a day.
In comes the unnecessary work of adding a second wordpress blog to the “shop” subdomain! Since i couldn’t gather any of the settings I used for the plugin when it worked, i had to redo everything from scratch. On the bright side, I do kind of like the idea of separating the shop from the main site and it’s a lot more cleaner as well. Here’s to hoping this plugin doesn’t crash and burn! Again!
It’s kind of a little terrifying working with these plugins. This one in particular, does have a development team but they aren’t doing much as to helping out individuals who need the help. In other words, their “Support” forum (notice the quotes) is bombarded with questions (of which I even posted my own with no reply) and hardly a post gets responded with helpful information. Topics from over a year ago are still left unanswered and demanded by newer users. Documentation is abysmal and out-of-date.
Why I continue to use this plugin you ask? Well, because it’s capable of doing functions i desire. Notably donation-based downloads. This is perfect for our “Pay-what-you-want” (User input price) MP3 downloads and it’s the only shopping cart i’ve seen that’s capable of doing it. Okay.. maybe that’s the ONLY function I really desire.
So all of that is done and i finally got the I/O site fixed up (minus the M3Us, i’ve still got to get on that). All that’s left is the i/o forum, which requires CSS modifications to match the i/o site.
more coding, great! tom is helping with that bit though.
on the bright side, i’m learning more as I go.
