Forum Replies Created
-
Posts
-
My recollection is that Thesis has historically offered challenges, not just Thesis 2.0 – and I’m afraid that I’m not really in a position to say how The Events Calendar 3.0 and Thesis 1.x will work together.
You can definitely try them out from the safety of a testing/development environment and give it a shot, of course, but the support we can provide at this point for any version of Thesis is very limited.
He Piebwa,
That would be understandably alarming. I’d like to build a better picture of what you are experiencing:
* Is the Events menu still accessible if you login to the dashboard?
* If so, is it possible to create and then edit new events? Are any pre-existing events still present?
* If you visit the plugin admin page can you confirm that the relevant plugins are indeed active (as it is possible that activation failed)your license key is out of installs … but as I only bought this in May 2013 I am not out of installs.
This doesn’t depend on the date when you purchased the license but rather the type of license and number of sites you have used it on.
For instance, with a personal license (valid for 1 site) if you install it on site-a.com (or a local development environment) and then set it up on site-b.com you are likely to encounter this message, however if that’s the case please just visit Accounts > Licenses and clear whichever URLs are no longer in use.
It looks like you are using the label within the href attribute whereas – based on what you are saying – you probably want the value, which is contained within $meta. Note also that you should quote the value of the href attribute:
Bad: <a href=url> Link text </a>
Better: <a href=”url”> Link text </a>You can certainly roll this up in a single function, I was really just giving you a starting point to work out from – but you might be interested in if/else or switch blocks here.
We don’t have a fix at this time (and sorry for any confusion that resulted from the cached FAQ page). All I can reiterate is that we plan on developing a tutorial or set of tutorials to support customers who also use Thesis 2.0 – but that is still to be actioned and we can’t project when it will be ready at this point.
I’m not sure what the content of the support emails you are referring to was – but it would be highly unusual for us to give a commitment like that with respect to any third party theme. That said, if we did indeed write that or otherwise wrote something that misled you then I can only apologize.
Thesis 2.0 is significantly different in structure from most other themes, particularly if a standard theme like Twenty Twelve is taken as a baseline standard. The reality of that from our perspective is that providing support in relation to Thesis becomes operationally challenging and we have therefore concentrated our resources in other areas.
I definitely realize that is going to be disappointing and if that means our plugin is no longer the right fit for you that’s also a disappointment on our end, but there isn’t too much else we can offer here.
I think a combination of The Events Calendar and WooTickets (plus WooCommerce of course) would get you 90% of the way there.
Multiple tickets per event can be purchased (and like other products they may either have an actual cost or be free). Customers can also have user accounts generated for them (for repeat purchases or, in this case, “registrations”) – though that is really a facet of WooCommerce rather than our stuff.
Printing and exporting attendee lists is supported and you should be able to manually create new orders through WooCommerce and see that reflected in WooTickets automatically.
Some things would require customization work, however, such as adding additional fields at checkout (if that is how you envision grabbing that extra info you need at point of registration).
Regarding payment modes, our plugins have no control over that but you should generally be able to use any gateways supported by WooCommerce (and its range of addons).
I hope that broadly answers your questions, but let me know if you need me to clarify anything 🙂
That is definitely a solid idea and something we wholeheartedly recommend.
As a general guideline, you should seek to:
- Make sure the hosting environment is the same as the target environment. For instance, if your production site will run on a dedicated box with Nginx, Ubuntu and PHP 5.5 your development environment ought to mirror that (rather than, to take something of an extreme, being within a shared hosting environment using CentOS, Apache and PHP 5.2).
- Take care of the details – something as simple but easy to miss as a PHP extension (such as CURL or DOM) not being enabled on one or other environments could lead to a hard-to-detect difference between the two installations.
- The same plugins and themes (identical versions) as are going to be used in production should also be used in development should be present in both cases. Indeed so should the version of WordPress be identical.
- You might also consider using a version/revision control system such as Git or SVN. This can let you track changes – and roll back in case of disaster – and also makes it easy to duplicate the same stack of plugins/themes to both environments, once you are at that point. Typically though this will not encompass changes in the database.
- In terms of backing up, there are lots of good tools and plugins that can help with this – search around and see what you feel comfortable with. If you have command line access to your server something like mysqldump can be fast and effective – but isn’t necessarily for everyone.
With the above said, I’ll leave the floor open for others to chip in with further advice 🙂
I know you all said you’ve done “heavy testing” with ECP 3.0 and Thesis, so this makes it extra disappointing to have this issue.
Sorry for letting you down on this one Derek – can I ask though where you saw references to the above?
I believe we are still planning on building a tutorial (or set of tutorials) to help guide Thesis users through integration, but that is still in the works and has not yet been released.
I certainly haven’t seen it so far on my test installations or a number of other folks installs – but that isn’t to say it’s not a very real problem.
Do you have any items in the trash (and did you upgrade directly from 2.0.11 or were you already using a copy of 3.0 beta)?
Indeed. Be aware however that a great deal of HTML output has changed structurally, so not all previous customizations will cleanly port across just by changing those directory/filenames, though it certainly may work in some cases and may at least form a starting point.
Definitely. In theory I don’t see why it wouldn’t be possible to make it work via SSL but I’ll need to get our dev team to check into that – bear with us as we’re slightly under resourced over the US holiday weekend but we’ll try to get you an answer as soon as we can.
Certainly, there is an entry in our Frequently Asked Questions section covering just that:
It looks as though the issue may be that your site is served via a secure connection but the Google Maps element uses regular HTTP (and so some browsers are blocking it for security reasons).
I don’t know off the top of my head if we can change this so HTTPS is used for those items (assuming Google support that) but bear with me and I will check in with the team.
Hi Kate,
There are a few threads about this and we’re currently investigating (many seem to relate to WooThemes’ offerings in particular but there seem to be other themes like your that are also affected).
One report suggests this may relate to the WordPress front page setting (in Settings > Reading) … can you confirm if you are using a static page as your front page?
