Endlyss

@sterndata

Okay, I can understand and roll with that. Apologies for the incorrect metrics, and thanks for the correction.

That actually puts good bit of that into a different perspective then.

Not sure how many active installs there are of Classic editor, exactly, since it stops at the 5,000,000+ mark. It’s been at that mark for quite a while…even though it has nearly 24 million *downloads*, not sure if -all- of those are still active.

@orlando

Lol “55 million downloads…there is no comparison.” Get real.

As if that number isn’t inflated by the fact that it is force-downloaded on new installs. The download count remains on a plugin, even after it has been uninstalled.

Instead, focus on the fact that there are only 200k ACTIVE installs of Gutenburg, and well over 5million ACTIVE installs of the classic editor plugin…don’t think that only 2000 reviews here represents ALL of the negative feedback that Gutenburg has received since the beginning. It’s only a fraction of it.

Don’t get me wrong…WordPress Core is managed by volunteers…but volunteer or not, you don’t ignore the actual feedback from a userbase as large as WordPress’s and just say “screw you guys, we’re doing what we want.” When people are still saying “this was a horrible update” 2 YEARS LATER, it isn’t just people not willing to “get up with the times”, it is “you made a horrible update.”

The only part I can really agree with you on is ye I guess it’s probably too late for it to be removed. With the portion of the userbase who’ve actually converted to the P.O.S., it’d break all their sites to backtrack now.

Nah we’re not “old”…this is just intrusive and there are much better alternatives out there, of which they make it pain to replace this with those.

• This reply was modified 4 years ago by Endlyss.

@trajektorijus

Still a typo in there that will cause a fatal error

There is an apostrophe missing after “woocommerce_product_archive_description”

so this:
remove_action( 'woocommerce_archive_description', 'woocommerce_product_archive_description, 10 );

should be this:

remove_action( 'woocommerce_archive_description', 'woocommerce_product_archive_description', 10 );

Thanks for the reply and confirmation that my idea would work!

In order to tackle the issue of defining many different plugin function sets, therefore creating excess, I’ll probably do what I do with SASS right now — treating everything like modules.

Have one main core plugin file, and each plugin that I am accounting for will have it’s own separate functions file stored within subdirectories. And then from there I’ll simply require_once their function files, only if I am using that particular plugin. If it doesn’t get “require_once”-ed, then it doesn’t even make it to parsing.

Okay, cool. Thank you for the info, Adam! I’ll go do my due diligence now and learn about authentication methods, then! (and thanks for the bonus info about 0Auth and basic!)

Thanks for the reply, bcworkz!

I apologize for taking so long to get back to you about this. I had been working on other aspects of the project in the mean time.

That makes perfect sense to me. I really appreciate the indepth response.

This particular action attaches meta data to a woocommerce order item. Is that considered a “special privilege”?

And in practice, is there any harm in verifying a nonce no matter what? For example, if in situations like this, where I am questioning whether or not I should, would it be bad if I just programmed a nonce-check anyway, just in case?

Your FontAwesome CSS Stylings need to be targeted to the widget wrapper.

For example, instead of “.social-feed-main-container .fa-facebook” you targeted just a very broad “.fa-facebook” which has messed up all social icons that I had placed on my site, because I also use FontAwesome

BAH…changing rating.

Just realized that the name for this plugin is the exact same as another, so when I went to install it via the WordPress plugin interface, I selected the wrong plugin.

I apologize greatly for the mistake! Now I’ve tried out the proper plugin and it works awesomely! Adjusting review accordingly

Gotcha!
Thank you very much for the response, bcworkz, as well as the explanation as to why it’s important.

Partially.

I got everything except the initial “This product is not currently in stock and is unavailable.” which is fixed by hitting update manually on a given product…I found this to be an acceptable solution, since it only required me to open the products list in the backend and bulk update posts.

However, if I could find a way to solve this, that’d be awesome. I am looking into Mike’s initial prices & stock comment, however I have to wait until I am off work before I can implement something. Will post back here once I do, as well as my cleaned code from above.

And thanks for the suggestion, Caleb! I appreciate it and will look into it as well, while checking out Mike’s.

But is that not what I’m doing with the whole “change_price_all_types” function? Or do I have to do that to the parent product as well, and not just the variations?

Also I ended up figuring out the blank attributes dropdown — It had to do with the attributes not being synced properly.

Once I clean up the code, I’ll post my solution. I still had to go through and hit “update” on all products, so if I could solve that, that’d make this piece of code a keeper, hahaha. However I was okay with that caveat, since I could bulk update posts.

Have you considered editing the “slug” on the individual product categories?

For example, the “Accessories” page would use the “accessories” slug, in its permalink.

And then you could change the slug for the category to “accessories-category”

To change this “slug”, you would head to your wp-admin dashboard, then hover over “Products”, then click “Categories”

Then you would open each category and add “-accessories” to the slug field (the slug field is found directly below the title)

So for example, now “product-category/accessories/hats” would become “product-category/accessories-category/hats”

You missed your query on the “if(have_posts())” in your custom query — so it’s querying every single post in the wordpress database to see “if” there are any (which of course there are), and then since you have the while loop only querying “have_posts” on the custom arguments, it’s only showing posts within that.

Essentially you’re asking it:
“If WordPress has posts”
“Show only these types of posts”

when you want to ask it:
“If WordPress has these specific types of posts”
“Show only these types of posts”

Once you correct that logic, it should respond to the “else” correctly.

<?php if ( have_posts() ) : while ( have_posts() ) : the_post();  ?>
<?php the_content();  ?>
<?php endwhile; endif; ?>
<hr>
<?php
   	wp_reset_postdata();
   	$args = array(
   		'category_name' => 'careers'
    );
   	$the_query = new WP_Query( $args );
	if ( $the_query->have_posts() ) :
		while ( $the_query->have_posts() ) :
			$the_query->the_post();
			?>
				<h3>
					<a href="<?php the_permalink(); ?>">
						<?php the_title() ;?>
					</a>
				</h3>
				<?php the_excerpt(); ?>
				<hr>
			<?php
		endwhile;
	else:
		?>
		<p>There are no job openings at this time.</p>
		<?php
	endif;
?>

Also one big thing that really expedites learning — keep your code organized. For example, my system involves nesting with the tab key. It helps me keep things in line so I can quickly follow the code down the page and see where I messed up. No offense, but your original code was a bit scrambled. I feel you may have been able to see the error, if it was more organized. You don’t have to follow the nesting organization like I did (although a lot of developers do), but figure something out, because it also helps you focus on the code more, and you’ll be able to spot mistakes more easily.

Best of luck to you, Vince. If you have any questions about the above code, or if it turns out that it doesn’t work, let me know.

Sweet. Thank you for the feedback .

1. Figured you wouldn’t, for this exact reason, haha — but was brainstorming so chucked this idea in there anyways.

2. Interesting…I am sorry. I had not taken volunteer number into account. With how active the forums are, and how big WordPress is, I figured there was like…thousands of you guys. Oops!

3. Can’t wait to see what happens when that gets into the mix! I’ll definitely still be around with WordPress when that happens.

4 (the bonus support/chat info) — Thanks for that, and the invite! I’ll bookmark these, and get slack setup later tonight. Been wanting to slowly inch into the volunteer stuff for a while, and recently hit a new job where I will be able to have time for it, so this is definitely appreciated. Thank you.