ArielZusya

Turns out I wasn’t on 3.5.1… I was on 3.5.0. Updating was what the doctor (@thomasplevy) ordered. Everything is working perfectly now. Thank you!

• This reply was modified 7 years, 8 months ago by ArielZusya.
• This reply was modified 7 years, 8 months ago by ArielZusya.

Looks like you’ve made some progress? I just updated my plugin but no change. Is there something different that I need to be doing? Were you able to replicate the issue on your end? Thanks!

It does hide it properly from non-members but it doesn’t display it properly for members. What I get for members is the shortcode returned so when I used the example above (changing 1234 to 1997–the free membership on my site), instead of displaying courses it displays [lifterlms_courses]. Same issue with the shortcodes built into The Core theme… instead of the content that the shortcode represents that I want, it gives me the long, setting-filled, shortcode. The Core uses a variation of the Unyson visual page builder plugin for its shortcodes.

Thanks! That would be great. I am already so impressed with LifterLMS… I will be even more impressed if you implement that change to allow shortcodes inside this shortcode that quickly. You folks at lifter are awesome! Thanks!

Also, am I correct that I cannot embed another shortcode within this shortcode? If I am incorrect, how do I do that? I’m using the Core theme (one of the ones listed on the LifterLMS site as being compatible) and it relies heavily on shortcodes for its visual editor. Thanks!

Fantastic! Thanks. Just to clarify, if I want to to hide content from unregistered users and in its place display a message, I would use the following shortcode:

[lifterlms_hide_content membership="1234" message="This content is for members only."]

This will only display to members of membership 1234

[/lifterlms_hide_content]

Also, I see that the “membership” parameter was removed. Does that mean I should use “ID” in place of “membership”? I see that “membership” still works even though it was removed. Not sure what the best practice would be. Thanks!

• This reply was modified 7 years, 8 months ago by ArielZusya.

Still no resolution.

Makes total sense. Thanks for the assist! Problem solved.

Aha! I think that solved it. Thanks for all the help!

Thanks for your responses. I took a look at both but I’m unfortunately still struggling to implementation. Here’s where I am… I am able to generate a page of posts that displays the name of the subcategories but and below each it shows a posts but the posts it shows do not correspond to the category name. I thought by placing my query_posts() in my foreach(): loop it would inherit the particular category but no such luck. Here’s the first attempt I made:

<?php  $cats = get_categories('orderby=id&order=DESC&child_of=5'); 

			foreach ($cats as $cat) :
				echo '<h1>' . $cat->name . '</h1>';
				query_posts( 'orderby=date&order=ASC' );
				    if (have_posts()) : while (have_posts()) : the_post(); ?>
					<?php the_content(); ?>
				    <?php endwhile; endif; wp_reset_query(); ?>

			<?php endforeach; ?>

I then thought I needed to drop $cat into the query_posts() args but I got an error doing that. Am I on the right track? What am I doing wrong? Thanks again for you help.

Ariel

Glad I was able to help!

Thanks again for your responses. I suppose what we’re trying to do is not do a 301… so we can continue having the old address point to the live site (at least for a while) at the same time as having the new address point to the same live site. Will that cause a problem for wordpress? Thanks!

Thanks for your response. I suppose what I want to confirm before doing anything is that I’m not going to run into trouble with a change we’re about to make. Right now the blog is at, let’s say for sake of this question, complicatedname.com. We’d like to move it to simplename.com. We don’t want to lose traffic, however, from those who don’t yet know the new name. We’d rather not use a redirecting page and instead use either a cname or ptr in our DNS to just point to the same content for each domain. I really ultimately have two questions:

1) when we make the switch, I should change the WordPress address URL and the Site Address URL from complicatedname.com to simplename.com, right?

2) if a user comes in to the site on complicatedname.com after the change, will that user suffer errors (even though the wordpress address and site address point to simplename.com)?

Thanks for your help!

Do you have your WordPress address and Site address pointed in the right direction? You might want to check out Changing_The_Site_URL on the WordPress codex. I hope that helps!

This might be too simple, but have you checked your user profile on WP? There’s an option to turn off the visual editor. Might be a good place to start if you haven’t already been there. Alternatively, perhaps it is plugin related. If you turn off the plugins does the visual editor come back? If so, you might try turning them on one at a time to see if you can determine the culprit. I hope that helps.