ironfish2

Hi,
Thanks for responding ??
It turned out I was not allowing javascript to run properly on my site.
My bad ??
Marking as resolved.

Hi, I am using the latest version of WP – I use a plugin that does automatic updates.
I do have cookies enabled.
Of course, now the problem has gone away.
It is maybe intermittent but will mark as resolved…..

Ok then

Thanks for explaining that there is a technical reason that the Title cannot be a block.
That github issue reflects my thoughts well.

@otto42

Fair enough ??

Just to reiterate, I dont mean to criticize anyting – It is more that a “Try it” release at this time I dont see this being fair to developers like yourselves who now have to deal with responding to millions of users, as opposed to hundreds in focus groups….but if you and the dev team are ok with it, then ok ??

• This reply was modified 6 years, 7 months ago by ironfish2.

@otto42
Thanks for your reply and explaining more about the product develpment process that G has gone thru.
I wasn’t aware it had already gone thru some focus groups.
I think that product development can be in different ways, there are different methodologies. I see a strong difference in the way I would do it (Having done it many times in my career) and the way it was seemingly done with G.
For that reason I will have to respectfully disagree with you that the product was ready for a Try it release.
Sorry that I did not use @otto42 – I was not aware that I would be accidentally pinging someone – I will use proper usernames from now on…

Hi Samuel and Marius thanks for your quick responses ??

Re the + Add block button:

The initial starting + symbol that appears below the title appears there when you have no content. It’s there to get you started by adding the first block to the document. After you have added that block, it doesn’t appear again.

@otto42:
IMHO as an educator with 30+ years experience, when you have a popup that says use THIS + button to add a block AND you place that popup right next to the + button that appears by a new block, you are teaching people to use that particular + button to add a block and NOT the one at the top of the page.

So it is then reasonable after you have just taught a new user to use that use that particular + button, to NOT take it away. It is unreasonable to take it away, AND NOT explain why you have taken it away.

Ie it does not make sense to tell a user to use that + button to add a block, and then think it is ok to take it away, and not tell the user why you have taken it away.

To the user, a button that was there a second ago has now disapeared without it being intuitively obvious as to why, without being explained why it is gone – so to a new user it has just gone “poof”.

IMHO that is like teaching a new user in Microsoft Word to go to File > New to create their first document, and then secretly removing the File > New menu item and not telling them you have done so or why. And now expecting them to find a different way to add a 2nd new document. And ignoring the fact that you have just created a negative and frustrating experience with the product when the user experiences seeing that the File > New menu item, the one they have been told to use, has disappeared…

Furthermore, when you point out the + button in a new block area, a new user may not even be aware as yet of the + button at the top of the page.

The second + add button at the top of the page could be assumed to be eg Add a post/page, not add a block, especially when you are presenting TWO + buttons initially. Ie why would you present TWO + add block buttons in close proximity to each other that do the same thing. If you have 2 buttons close by one can assume they have different functions, why else would you put two together so close by?

Yes the + at the top of the page has a Tooltip but will a new user a) be aware of the + button when you are pointing them to the other one, and if a new user is aware of the + at the top of the page, will they always automatically know to hover over it to learn what its function is?

Of course the other question that begs to be asked is this:

If the + button next to a new block is removed after inserting the first block, and you have say 20 blocks, are you going to make users scroll up to the top of the page each time to insert a new block? Makes no sense.

It makes more sense to remove the + Add block button at the top of the page….

Furthermore as Marius says:

There should also be a “Add new” button if you hover the bottom or top border of a block.

I had this experience in using previous versions of G – I did notice always a + button when hovering around a block so it is reasonable to expect it to be there for all new blocks, not just the first one.

Why was this removed?

Re the Title block/area/field whatever it may be called:

Thank you for your understanding of this Marius. All this time wp has touted G as being blocks blocks blocks and more blocks and then the first field (Title) that a new user would fill in is not called a block and looks nameless to me – if Title field has been selected then G says what has NOT has been selected, ie a block has not been selected, yet the user has selected something ….this just does not make sense. Better to explain to the user what has been selected….

That leaves what I said earlier:

I read somewhere a while ago that if the last block is a paragraph then no + button will be shown. I saw this on a tweet from ACF with the word “What?” I agree.

Is this still true?? I guess you want the last block to always be a paragraph – that would be the reason to not show a + button if the last block is a paragraph BUT this is IMHO NOT the way to enforce the last block to always be a paragraph..

Thank you both for your consideration of my feedback…..

PS I do think that this plugin is WAY to early to have been released to the general public – it should have been shown to test or focus groups, it needs a huge amount of work – esp in user experience, UI, workflow, etc – it was far too early to release a “try G” to millions and millions of users….

I dont see this being fair to developers like yourselves who now have to deal with responding to millions of users, as opposed to hundreds in focus groups….

• This reply was modified 6 years, 7 months ago by James Huff.
• This reply was modified 6 years, 7 months ago by Steven Stern (sterndata).
• This reply was modified 6 years, 7 months ago by ironfish2.
• This reply was modified 6 years, 7 months ago by ironfish2.
• This reply was modified 6 years, 7 months ago by ironfish2.
• This reply was modified 6 years, 7 months ago by ironfish2.
• This reply was modified 6 years, 7 months ago by ironfish2.
• This reply was modified 6 years, 7 months ago by ironfish2.
• This reply was modified 6 years, 7 months ago by Samuel Wood (Otto). Reason: Fix username so poor samuel doesn't keep getting pinged

Hi Michael:

I’m not sure what the problem is, other than an aesthetic one.

Ok, well here are the problems as I see it:

1) Your plugin is listing private CPTs to users when it should not

2) Your plugin lists Posts three times, and it there is no definite way to know which one is which CPT

2a) If a user selected the wrong Posts, then your plugin would not add SEO to the right Post type. Things would not be working properly. That is technical issue and definitely NOT an aesthetic problem.

3) Suggesting a trial and error solution to a problem that should not be there in the first place.

4) If you dont see the problem, why have you created a github ticket for it?

As for suggesting:

a) It’s most likely the first one, next to pages.

Yep, that is what I just said, prior to your last post.

b) You can figure it out by trial and error (max three tries).

Yes, that is why I said I will try the first one, prior to your last post.

PS you are welcome for me taking the time to identify by plugin the cause of this issue and working with both plugins to identify things further and suggesting resolutions. Sorry I bothered you with this non-existing problem.

• This reply was modified 7 years, 4 months ago by ironfish2.
• This reply was modified 7 years, 4 months ago by ironfish2.

Hi Michael,

Thanks for creating a ticket about this issue.

As for ignoring the extra ones, since they are all 3 called Posts, I can’t do that ??

One could guess that the first one in the list is the correct “Posts” but there is no distinction that sets them apart.

I have up until now checked all three to have SEO applied to which I am sure adds processing overhead.

I will try it with just the first Posts checked.

• This reply was modified 7 years, 4 months ago by ironfish2.

Hi Jared,

Thanks very much for your quick and concise support.

If possible, please consider – give your private posts types a suitable descriptive name, so that they do not show up as “Posts”.

In any case your support has been appreciated.

Hi Jared,

Thanks for explaining, both here and at the issue that I posted with your plugin at https://www.ads-software.com/support/topic/issue-being-caused-by-wpforms-plugin/#post-9703200.

Presuming Michael would agree that this is the cause, could I ask you to consider the following:

Jared – If possible, give your private posts types a suitable descriptive name, so that they do not show up as “Posts”.

Michael – If possible/suitable, show only public post types in your list of CPTs to apply SEO to.

In any case thank you both very much for your help.

Hi,

I am really sorry but I linked to the wrong issue.

Here is the correct issue:

https://www.ads-software.com/support/topic/seo-on-only-these-post-types-lists-posts-multiple-times/

Sorry I was not clear.

All in One SEO Pack has a section where you can select which custom post types to apply SEO to.

With WPForms Lite activated, the list shows as:

Posts Pages Media oEmbed Responses Posts WPForms Logs Field Groups Fields PayPal IPN Listings Google Font Controls Posts

So the Posts post type is listed three times.

When WPForms Lite is deactivated, the list shows Posts only one time.

So it seems to me that WPForms Lite is creating/adding two more Posts post types when it is activated. Of course, there can only be one.

I can see that WPForms Lite is creating a custom post type called WPForms, and so the plugin may also be creating other custom post types but incorrectly naming them as Posts…..

You are right ??

For future reference for anyone else that may have this issue:

Issue is being caused by WPForms Lite plugin.

Thanks for your help.

Hi, what I meant to say is that I don’t see any markup at all.

Eg if I search for “schema” in the source of a page, I can’t find it.

I would presume that:

Eg:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  [Any added info by your plugin added here]
  }
}
</script>

would be present in the source of the page.

I presume this because you say:

We don’t add all of that information as schema.org markup at the time, however we’re working on adding more.

ie some info is being added.

Is anything being added at all?

I am concerned that the plugin is programmed to add some schema info, but in my case it is not adding any at all due to an error.

• This reply was modified 7 years, 4 months ago by ironfish2.
• This reply was modified 7 years, 4 months ago by ironfish2.
• This reply was modified 7 years, 4 months ago by ironfish2.
• This reply was modified 7 years, 4 months ago by ironfish2.

Thanks again.

I have already left a review ??
https://www.ads-software.com/support/topic/great-plugin-great-support-great-documentation/

Cheers