|
Brian Hartman
|
September 5, 2012 at 10:16 pm
Hi,
I just successfully tested our pay pal pro integration but after the transaction, the auto return page takes the customer to this page:
http://photoelan.com/download/autoreturn.png
why is that, it looks all unformatted or something.
Brian
|
|
Seth Shoultes
|
September 5, 2012 at 10:47 pm
Without looking at the actual website, it looks like the theme is not loading the shortcode properly. Can you try testing with a different theme really, just so we can try ruling it out?
|
|
Brian Hartman
|
September 6, 2012 at 10:08 am
Thanks Seth, a couple things…
I looked at my Auto Return page and “Force SSL” was on. Des that make a difference?
I tried changing themes and it appeared to work: http://photoelan.com/download/autoreturn2.png
Is that what its supposed to look like.
Also, we can’t change themes. Can we get this working with our existing theme?
Thanks,
Brian
|
|
Seth Shoultes
|
September 6, 2012 at 12:48 pm
Hi Brian,
Our support might be able to fix the theme conflict, but we will need you to purchase a support token to cover their time/costs.
|
|
Brian Hartman
|
September 6, 2012 at 1:23 pm
Hey Seth, I appreciate the option, however we’ve been spending and spending and toiling to get this PayPal pro integration going so I’m going to look into fixing it with a friend or with the theme developer where we purchased the theme first.
|
|
Brian Hartman
|
September 10, 2012 at 1:45 pm
emphasized textSo I checked with our theme developer ProPhoto Blogs and this is what they had to say:
“Brian, You are right, there is something in the way ProPhoto is designed that is not working well with that plugin. (Event Espresso) Again, I apologize for that. In general, we don’t do individual site customizations, although years ago, Jared did more of that sort of thing. We now put all of our time into developing ProPhoto to the point that it is flexible enough to accommodate a great range of possibilities. With thousands of users, editing the theme to accommodate a single user’s unique usage, isn’t possible, especially when it is related to a plugin that we don’t own and can’t control. We have no assurances that the fix won’t be broken with future changes that the plugin does or does not make. Any edits to the theme files must make sense for all of our users as they are completely replaced every time we push and auto update. Obviously, it’s not accommodating what you are wanting to do. I’ll connect with our development team today and see if they want to take on your case. It is likely, however, that their communication will echo mine. Again, I apologize for the frustrating experience that you are having. Expect to hear from me or our developers soon with regard to your request.”
So this is kind of bad for me because if EE is going to be problematic, I have to make a decision to keep one or the other and I’ll probably keep the theme at this point. That means I’d need to use eventbrite.com or something like that. I don’t want to do that but I’m not going to deal with the hassle of having to do a code fix again and again every time my theme gets an update. Thats too expensive and too much time in maintenance.
Am I being unreasonable or do you have some other suggestion. Before discounting the theme consider that the look and feel and ease of user customizability is huge for us especially given the price point for this theme. That being said, we have been looking at having a custom coded blog/site to replace the whole thing so that the specific things we need are there in a tight package and we can bring our blog and site together in one place.
Thoughts?
Brian
|
|
Seth Shoultes
|
September 10, 2012 at 2:17 pm
If the theme supports it, you can try adding [raw][/raw] tags around all of the Event Espresso shortcodes. If it is not supported the theme already. This is something that could easily be implemented by the theme developer and most themes that are on the premium theme market support this.
I am not sure what to say about the theme developers response, other than the fact that that is a pretty standard response for theme and plugin developers. We really cannot support every single theme that is out there. Especially if the theme developers refuse to abide by the theme/plugin guidelines that have been implemented WordPress community. I mean we are using a pretty standard shortcode format and have followed the WordPress guidelines for outputting the content that is output by our plugin. Our plugin is also used on thousands of other WP installs and we have never seen this problem.
If the theme developer keeps changing things and breaking you custom code, then maybe you should consider not updating the theme. If you decide to use another service, then that is up to you. However, we would much rather see you continue to use EE rather than wasting yours and your customers money on third party fees.
|
