Forum Replies Created
-
AuthorPosts
-
nickthegeekMember
Kevin,
One leg of support that is still being built, which will bridge this gap, is the knowledge base. We can take the information from common requests and convert that into a searchable knowledge base.
nickthegeekMemberThat should work but it doesn't create the correct media embeds so some readers won't like how that formats.
nickthegeekMemberedelster,
Please log into my.studiopress.com and look at your download page. Next to the download link is a "setup" link. The setup tutorials explain how to make this change.
nickthegeekMemberThe setup link in the my.studiopress download page should take you to their forums if available.
November 21, 2012 at 9:40 pm in reply to: When to use forums -vs- when to use support request? #1237nickthegeekMemberJohn is right. Technical issues and usage are handled in the new ticket system. That is what the "how do I" and "technical" options are for. Customization is handled in the forums so the community can help out and benefit as usual.
nickthegeekMembernickthegeekMemberIn the widget settings. You have [post_info] for the post info field. This is not a valid short code. Add the code you are using to create your date format. I don't have the exact code because I don't know what code you are adding.
nickthegeekMemberDavid,
Actually this was snuck in without much fan fair when it went up to v. 1.0. This code should work
add_filter( 'agentpress_listings_post_type_args', 'child_agentpress_listings_post_type_args' );
function child_agentpress_listings_post_type_args( $args ){
$args['rewrite']['slug'] = 'listings';
return $args;
}nickthegeekMemberRedwood,
You can make your code conditional. Here is a tutorial I wrote to help with this. http://nickc.co/conditional-content
nickthegeekMemberKJA,
This is a known issue. The coupon post went out before we had everything in place for it here. It doesn't affect new customers, just the existing customers. Give us a bit to get one of our developers to resolve this issue. Thanks for your patience.
nickthegeekMemberNick,
Sorry for the transition issue. Please use this form to request help.
http://www.studiopress.com/account-assistance
nickthegeekMemberNot really, both require replacing the plugin content output with your own custom output.
nickthegeekMemberJason,
That is more difficult. To get it to work correctly you actually need a media container. I am looking into the best way to handle this in general and will make that available in a plugin update.
nickthegeekMembertbray09,
As Sozo shared, we are relying on users to tag their threads. Please put in relevant tags such as the theme you are using. This will make it much easier as things develop so that users can search by theme.
nickthegeekMemberThe change is actually based on many different problems with the previous system plus the desire to use our own product (Premise) to handle things. Also we are a WordPress company so it makes sense for us to use WordPress services (bbPress) over other services.
Some of the issues we had with the previous system include limitations on downloads and the inability to allow ProPlus members to get new themes without using the forums to deliver the downloads. A lot of users were very frustrated with this delivery system as were we. my.studiopress is about making a one page system that all users will have access to so purchases are available without going through hurdles.
We also had problems with users registering for support. The old system required a purchase, then a download link and support email were sent. Because of the way the system worked they had to register for a support account then upgrade that account. This system had so many "moving parts" that things broke regularly. You wouldn't believe the number of times users weren't able to get to support or even tutorials because of this system. The new system gives immediate access to tutorials and the technical and usage support in one step. For customization requests there is one more step. It is so much simpler and things break less often. When we find something broken we can fix it because it is our system. We developed it and the developers are on staff. It's a pretty good scenario for making sure things work and that is best for our customers.
Speaking of support, in the old forums users created a thread and then needed to wait till we could answer it. If they replied to a thread before we could or if someone innocently said "yeah, I've got this same problem" we would miss the thread. That is a messed up support model. It was fine when we fielded 50 or so threads a day. We could go and looks to see if things were missed pretty easily. Towards the end I fielded 75-100 myself each day, and I know the other moderators were fielding a ton too. We had so many threads that we just missed literally dozens every single day. Last January we went through and made a solid effort to find every single thread that was missed. It took a couple hours every day. We did this for a month and we had an average of 20 a day back then. Requests were only going up so missed threads only went up. That is a seriously bad support system. It makes us look bad and it makes our customers very frustrated. Users that learned the system didn't make this mistake so that means the ones who were getting the brunt of this are new customers, ones who don't know how much we really want to help everyone. That frustrated us the most.
Another big problem we had, there wasn't a good way in the old system to tag team. If I took a day off (heaven forbid) then anyone who I was helping had to wait till I got back. Sometimes I even like to take a whole week of vacation, and that means people had to wait a whole week for my to get back and answer them. That is not how you do support. Under the new system I can tag the other staff if I think they are better suited to answer the question or they can tag me in. If I take time off they can see all my waiting tickets and respond. It is much better for us because we can actually take some off and not think "man I can't enjoy my time off because I know there are people who think they have been abandoned." It is better for the customers because they don't feel abandoned when we take time off. It really is a win for both of us.
I could keep going on this. We had so many meetings before things got started where we listed every bad thing and every good thing about how the old system. The lists are long on both sides. Ultimately we knew we had to keep community forums because we have an AMAZING community. We also knew we needed a support system for technical and usage issues that didn't lose customers.
We know the system we have now isn't perfect, but it is a system we own, so we can continue to develop it to adapt to the needs of StudioPress and the needs of our customers.
nickthegeekMemberLooks like you added "[post_info]" as your short code. This isn't actually a short code. You will need to add the actual markup that is in the post info to the output.
nickthegeekMemberHere is a tutorial on adding a custom post type to the main RSS feed
http://www.wpbeginner.com/wp-tutorials/how-to-add-custom-post-types-to-your-main-wordpress-rss-feed/
The post type is "video"
nickthegeekMemberJeff, There really isn't a simple way to do that. The issue is that the read more is part of the content output, so you would need to make your own custom content and a custom short code to output the more link in the post meta section.
nickthegeekMemberI was going to recommend that same series. I try to break it down and follow more or less the same path I took as I learned Genesis with an emphasis on learning how to use the files to find things like that.
nickthegeekMemberIt can be a beast since it can occur in more than way. If you are lucky you can fix it by:
[LIST]
[*]Replace all WordPress files except the wp-config.php file via FTP with a new clean download from wp.org
[*]Delete all themes you aren't using including Genesis
[*]Delete all plugins
[*]Upload a new copy of Genesis and remove any malicious code from the child theme. Since the child theme is simple it should be easy to identify code that wasn't part of the original theme or code you added.
[*]Log back into WordPress and change your password
[*]remove any users you don't recognize
[*]upload your plugins again, make sure they are clean copies
[*]change FTP passwords and do a virus scan on your computer and any other computer that has FTP or admin access to the site.
[/LIST]You should check out this article
[url]http://www.copyblogger.com/wordpress-website-security/[/url] -
AuthorPosts