vincentjflorio

If you weren’t aware, one of the “anything productive”s not mentioned is that the export allows for a find and replace, including serialization.

You can still not like it, of course, but in case that would be useful to you, I figured I’d share. Sometimes things like that are hidden by default.

I hadn’t thought about that. Instead of having a plugin to bring classic back, make Gutenberg a plugin but force it to be there by default and activated by default so that it’s still everyone’s initial experience and you don’t have to hunt for it.

I have no idea how much work would be involved versus the plans now, but it seems fair as the next transitional phase.

I am not that guy, but I just got the plugin to finally work, after a few attempts. I’d check and it’d break and then I’d tell myself to come back after a few months and try again, so kudos on the progress.

This may seem like a small thing, but I am trying to think of the standpoint of one of my clients rather than as myself, who knows how to do stuff in a few different ways.

There are a lot of page builders that direct people. Tutorials help, so I won’t pretend like some of them don’t need some instruction, but in at least one, when there’s a blank page, there’s a big button that says “Add New Section.” It’s brightly colored and the only thing in the display of the page. It’s obvious what I have to do to get started.

Granted, on here, there is “Add Title” and “Write Story,” but I have precisely zero clients with just a blog. Half of them don’t have one, and this comes up for me when I make new pages. Seems like a small thing, because common sense would say that anything could go in there and it doesn’t have to be an actual story, but in my experience even the brightest people are their dumbest selves online.

The people I know are some of the best in the region or even their industry, and I know some of them will say, “Story? I don’t want to write a story here, I just want to talk about my product or service.”

Not only that, but far more practically, I can’t seem to get rid of a title. Soooo many people don’t want a title on their pages, even after they’re informed that it can be detrimental to SEO.

Perhaps my biggest concern, though, for UX, is the teeny tiny (+) button to add new blocks. Sure, if I do it once I know where to go, but it is very small and has the same “weight” visually as buttons that do other less important and very different things. Why not make it a focal point if it’s something I will click a bunch of times when setting things up? If my vision was a hair worse I’d think it was a close button in the wrong spot.

I don’t know if it’s intentional, but I have a (seemingly auto-generated) max-width on the editor container which smooshes all my content into a middle area. 636 out of a 1920 screen, but more accurately about half of all usable space in the editor. That’s not representative of my theme at all. The classic editor isn’t either, because it also is on the back end, but it’s way closer and therefore more representative.

One of the thing people seem to like about “building blocks” and page building systems is the ability to easily do, visually, what you can’t easily without knowing HTML, doing things side by side on the same row, for example. Not only is it not clear how to do this (for two images that are small enough…I got it to align next to some text okay), but in my attempts at experimentation I wound up making something that looked broken (though it isn’t).

I saw that there was an undo, but it toggled back and forth, instead of back more than one step, and to a state that had never actually existed (no console errors, so I am not sure what it thinks happened. There are only three or four elements). Contrast that to a page builder with not only more undos, but a whole list where you can see it all live when you click them. I’m sure there are memory/database concerns (or maybe this is a planned feature), but in my experience people don’t give a hoot about how a thing gets done, even if there are consequences, just that they get what they want.

I don’t even know what’s possible, playing around with this, and I’d used WordPress for eight years. I feel like very little is, or that at least my options are super limited. I hate to sound overly dramatic, but I actually felt a little stressed, like a chest-tightening, thinking I was being restrained somehow. In contrast, my favorite page builder is so out of the way of the process of creation that I feel like it “falls away” and lets me just come to build my content unobstructed. That’s supposed to be the whole point, I think. “Come to WordPress, where you can just pop in and make stuff and pop out.”

I see guys that do custom web work around me and they poo on WordPress saying that it’s “just one more thing to learn” and that it has a huge learning curve, and I used to defend them saying that was not the case, that anything you needed to know could be mastered in a couple passes. That most of the issues people ran into were from people buying themes from market sites that were one-size-fits all and a lot of bloat that didn’t ride piggyback on the actual existing good parts of WordPress and tried to do their own thing unnecessarily. That actual WordPress, on its own, all the stuff you really need, is fine, and that their criticisms were about something else, not WordPress.

I am actually far less concerned about things like plugin compatibility, even though I am a dev, than I am about WordPress itself being “out of the way.” I get moving away from something like the classic editor when people had to find their own solutions (like page builders) to stay happy.

So I see the overall intent, and some of the vision, but I am going to need to play with it more and make attempts at generating specific layouts before I do an actual review. I have support tickets to issue first (I tried previewing an existing page after seeing it condense everything I’d written before into a single goofy column (which is fair, it was probably hard for it to convert it to blocks, if it tried), but then I got a 500 error the very next moment and I can’t access my site.

My folks raised me to say something nice after criticism, even if it’s meant constructively, so I will say that showing options for blocks on the sidebar (where the page templates and publish button go) is pretty nice, versus having pop-ups obscuring things like before. Makes it feel kiosky. Oh, and it is really fast.

Thanks for your time and patience. For all of our sakes, I wish you the best of fortunes. Thank you for still allowing the old editor for the time being and for working with so many developers to make sure all our other tools don’t break when release happens =)

For anyone reading, Postman SMTP is no longer available through that link and this may be why:

https://www.wordfence.com/blog/2017/10/postman-smtp-plugin-unpatched-vulnerability-removed-directory/

Wow, with how busy you are covering so many bases online, I didn’t really expect a response, especially so soon. Thank you for your commitment (even if you hadn’t responsed =)

The variations endpoint is actually the first thing I tried, but I couldn’t get it to work. It was of course never broken , I just didn’t fully understood what I was doing. I had everything from the documentation samples on there, but it wouldn’t click.

As it turns out, my problems were three-fold:

1. I was trying to make it all happen at once, which is probably a bad idea from a modularity/NSPOF standpoint anyway.
2. Even though the documentation explains it clearly, I thought the ID when making a variation was something that was returned from somwhere else or generated on the fly, perhaps referring to the parent. It really is just the ID for the attribute, which is independent from products and can be referenced manually or pulled with a ‘get’ from a product that happens to have it already assigned.
3. For whatever reason, the docs have ID and ‘option’ and just that didn’t work for me; I could make something new and the price showed up, but it didn’t assign the variation’s name to it. I think I figured if the option was “XL” that it would pull that down since that was an existing assigned option name. Adding “Size” (which happens to be one of my attributes) along with the other two pieces made sure it not only got made, but automatically assigned itself to the appropriate option.

To my joy and surprise, in spite of myself, it works instantly! When I viewed the product edit page, I checked Variations and they were already built out, just as if someone had pressed the button and gone through it manually!

Amazing! God bless! =)

I have my product creation tied to an event, in this case user registration. If the names are identical, as I’m sure you’ve seen, it doubles up. It might keep the pretty name, but the address does the normal WordPress behavior or concatenating the URL, like “monkey-claw” and “monkey-claw-2.”

In the REST API documentation samples, they always print out the actual command because it returns a response. When I instead load that response into a variable, I can parse it. This comes in super-handy when I need the product ID because, well, I have no idea what it is because it just got made two seconds ago automatically and they seem like they skip a bit sometimes.

In my case, I needed to change the author. I don’t think that’s supported by the API but the flipside of that is I don’t think it can be hurt when everything evolves; I don’t think it’ll break in the future. So I just used normal WordPress functions to update the post_author meta (I don’t want people editing other people’s products =)

I say all this to say…while I don’t know how to interrupt or filter the process itself, perhaps you can do something similar to wait till the product is made normally, unimpeded, nab its ID that gets returned, and then quickly update the name or URL to whatever you need it to be?

Like this:

$created_short_sleeve_product_response = $woocommerce->post('products', $short_sleeve_data);
		$created_short_sleeve_product_response_ID = $created_short_sleeve_product_response['id'];

Of course those are crazy long variable names, but you get the ID. Now any API or standard WordPress method that needs me to specify an ID, like update_post_meta, can get handed it on a platter, even though it should still be a mystery since it just happened and wasn’t manually assigned.

Does that help?

Thank you. I read about the problem more broadly on Stack Overflow about the potential issues of declaring those outside of functions.

This is the second thread about this I’ve come across in as many pages and the first with a solution (and it works). Since it only seems to come up as a notice in debug mode, many people might not know about it and it perhaps could be baked into the next update?

This condition is located in the description:

Automatically generate, email and download PDF documents with Gravity Forms and Gravity PDF.

and rather explicitly under Requirements (pay special attention to the last line):

Gravity PDF can be run on most shared web hosting without any issues. It requires PHP 5.4+ (PHP 7.0+ recommended) and at least 64MB of WP Memory (128MB+ recommended). You’ll also need to be running WordPress 4.2+ and have Gravity Forms 1.9+.

Therefore, it isn’t a stretch to conclude that saying it requires Gravity Forms is merely a summary of the product, not a criticism of it. Certainly not criticism enough to knock it down two whole stars.

I’d also point out that the free plug-in depository (and this is a free plug-in) is no stranger to plug-ins that depend upon, or piggy-back on, other plug-ins. This was purpose-built to make use of the Gravity Forms framework. It even co-opted part of its name.

Additionally, the Gravity Forms subscription itself pays for initial access to the product, yes, but afterwards simply to continue updates and support. Meaning that past a certain point, it isn’t even technically a requirement to pay to use Gravity PDF since neither it nor the main Gravity Forms plug-in stop working without that subscription.

All this is for the sake of clarity; the plug-in developers can speak for themselves and I am not trying to position this as a “defense,” especially since it’s not under attack.

I don’t want people to miss out on the opportunity to use this plug-in. The word “review” is used above but there isn’t one; there is not a single detail provided about what it offers or how it operates. The verbiage “if it works well” seems to indicate an attempt wasn’t even made to use it or install it, so clearly there’s no basis to assign it any value in a star system, good or bad, because it hasn’t been used, just merely speculated upon.

The ultimate irony is what a crazy good deal it is, since everything you get from this plug-in is offered as a paid service, but for a couple hours of reading and testing, even a beginning developer can make impressive-looking documents on the fly that more than rival most actual desktop software. I still don’t understand how they afford to both release it and maintain it for free, because it could cost a grand and I know people who’d jump on it.

PHP is the only server-side language I know, and I know as much as someone would after reading a bunch of tutorials (although I have a lot of experience at that level =) and we used it to build paper receipts and membership cards for an entire flag football league, including hitching it to the PayPal add-on and having both the office admin and the player each get sent their separate e-mails with attachments.

I always read the terrible reviews when looking at a product, so I’d never discourage people voicing their opinions. No developer is a saint and no product is perfect. Unfortunately, all across the plug-in repository there are people either using reviews for support (right next to a link for support) or reviewing something they haven’t used. If that doesn’t go away, it at least needs to be clarified each time by someone with legitimate trials in using the software.

• This reply was modified 8 years, 4 months ago by vincentjflorio.

The actual developer can clarify, but in practice what has worked for me is loading

SunshineFrontend::$current_gallery->ID

into a variable, and then making a conditional where I see if it matches

get_the_ID()

Since the latter will always return the “wrapper” page, and the current gallery ID doesn’t return anything on the wrapper page, they won’t equate.

More simply, what I’ve wound up doing in practice so far looks like this (ignore the huge, descriptive variable name):

$gallery_real_post_ID = SunshineFrontend::$current_gallery->ID;

if ( is_sunshine() && $gallery_real_post_ID) {

    /* Do gallery-only stuff */   

}

Keep in mind there are/may be other types that aren’t the single gallery, so if you do an “else” it could wind up on every last thing besides the single gallery pages (I don’t know, I honestly haven’t gotten that far).

I have been doing big hero image headers using the gallery featured image and placing it above the start of the actual Sunshine content. Obviously there’s no place for that for a gallery listing page (like “Client Galleries”), at least not with that specificity. It’s working great for me so far.

I use Genesis so I like to stop and inject code all throughout the process, and the whole “one page spits out everything” set up presents really well (seamlessly) but I haven’t yet gotten smart enough to work around it without extra steps like this in order to add my own markup.

Glad it helped! It kept getting overwritten for me so I copied my patched version into my theme’s /js/ folder, and used functions.php to knock the plugin copy of the script out of the lineup and always use my patch.

Might not be stable forever, in case there’s a security issue or upgrade or something, but for now it’s getting the job done hassle free.

Wish I knew what caused it to begin with.

add_action('wp_enqueue_scripts', 'wpse26822_script_fix', 9999);
function wpse26822_script_fix()
{

    wp_dequeue_script('masonryInit');
	wp_enqueue_script('masonryInit-patch', get_stylesheet_directory_uri() . '/js/masonry-init-v3-lazy.js', array('jquery-masonry'), '3.0.2', true);
}

Thanks, that worked perfectly! How did you arrive at that?

Whoops, the “/ resizeProportion” shouldn’t be in the first one. That’s a variable I only declare in my part and isn’t found in the file. Sorry!

I was going to donate to hear the backstory, but it said my amount was invalid, even though the field was set to USD. Is there some other way I can donate?

For what it’s worth, I had a similar issue and the matchHeight jQuery plug-in was called on the page (accidentally) but not loaded, so it killed every other Javascript process afterwards, including this plugin’s.

Fixed my own error and all is well again.

Freaked out for sure, though =)

If you go into genesis-featured-content-widget/widget.php

you’ll see the following code about a fifth of the way down the file:

$image = genesis_get_image( array(
				'format'  => 'html',
				'size'    => $instance['image_size'],
				'context' => 'featured-post-widget',
				'attr'    => genesis_parse_attr( 'gsfc-entry-image-widget', array( 'align' => $align, ) ),
			) );

I just switched $instance['image_size'] to 'full' for my own purposes and it works fine.

It’s not clean, it will erase in an update, and it certainly doesn’t affect the drop-down, but I don’t have the time to figure out how to do it properly just yet, and the front end result has zero issues.