[Henriët]

Hello Mahesh,

thank you very much for your quick reply! I feel so foolish… you are absolutely right.

Had checked this on posts even though I hardly ever edited/played around with the default layout settings there, but never on this page as I thought it was now automatically generated, having no influence on the layout.
However, editing the layout was exactly what I had done on this very page when it was still a “normal page” a long time ago, and apparently I had not reset it.

Reverted it to the default layout, saved it, and of course now it follows the new settings!

I’m very sorry I troubled you with my sillyness, but I’m also very happy that it is sorted 🙂

Kind regards,
Henriët

[Henriët]

Hello Pratik,

Thank you for the correction!
I see what you did there, and that makes the code complete I think 🙂

Had noticed that the archive was missing, so I had already altered your first line of code a little bit into:
elseif ( is_active_sidebar( 'sidebar-optional-archive' ) && ( is_archive() || is_home() ) ) {
and for some reason that did exactly what your new line does too. Your new line is more complete though, so I have inserted that anyway.

Kind regards,
Henriët

[Henriët]

Hello Pratik!

Yes, you saw correctly that I’m using a childtheme, it’s so much better than changing core files.
I really thought that the line as it was called for the “archive sidebar” for the blog page, but you’re absolutely right, of course.
Followed up on your suggestion and it works perfectly.

Thank you very much for your quick help! 🙂

Kind regards,
Henriët

[Henriët]

Hello Mahesh,

Thank you very much for this quick fix, I just installed the new theme version and it works perfectly now 🙂 Makes me happy!

Best regards,
Henriët

[Henriët]

Hello Mahesh,

thank you very much! I’ll be waiting for that fix then 🙂

Regards,
Henriët

[Henriët]

Hello Mahesh,
Thank you very much for your help!

Noticed that the part for the author was indeed what I had seen previously, so I’m very happy to know that that was the best way indeed 🙂

The second part for the category tags worked, but not completely as I had intended. It didn’t seem to work on the post itself (category was still at bottom), but the biggest problem was that the tag did not appear on the same line as the date.

However, I did help me further!

Guided by your solutions, I discovered that both the lines for date and category were <p class=”meta-entry”> and so I went looking for a way to combine them. After several attemps I managed to include the category into your code given to remove the author.
In the gridalicous-core.php I then found the function that defined gridalicious_tag_category, and it turned out to be a <p> indeed, causing it to appear on a line by itself.
Copied that part above the given code, replaced, <p> with <span> and that did the trick!

Everything is neatly on the same line now, and I didn’t need to use the content.php file anymore. Removed the tags at the bottom by css. 🙂

Thank you very much for helping me out 😀

Best regards and much appreciation for your help,
Henriët

[Henriët]

Hello Pratik,

Just a follow-up 🙂

I’ve found the piece of coding that caused the conflict.
It was in reordering/customizing the shipping fields, which share the column with the “create-a-new-account”-button.
I copied the code from a trusted php developer; it looks like he overlooked this tiny checkbox, accidentally removing some code with it. 🙂 I have contacted him, and hope that he can solve this!

Thank you very much again for your input that got me in the right direction.
Since this appears not be related to Gridalicious after all, I won’t bother you about it anymore!

Kind regards,
Henriët

[Henriët]

Hello Pratik!

Ah that was a miscommunication then… Please don’t think that I was impatient, I know you’re very busy. I just suddenly realised that my reply could be understood as if the problem was solved and I was afraid that you might have seen it that way!

The only template I’ve overridden was cart.php of woocommerce, and the only thing I’ve done there was remove the two links from image and product name to the product page. Worked perfectly.

However… very silly of me, but I didn’t check on the parent theme before (only on Twenty-Sixteen…) as all my custon css and custom php went smoothly and did what they were supposed to do.

Now I did though and I can confirm that the fields do appear in the parent theme. Therefore, the problem must lie within my customisations after all. I’m a bit ashamed of that!
Before throubling you with my child style.css and child functions.php (which are mostly in English, so no foreign language there ^^), I will remove them completely and re-add them step by step. That way I should discover the culprit.

I will let you know if/when I’ve found it (or not).

Thank you so much for your time so far and pointing me in the right direction 😀

A happy customer,
Henriët

[Henriët]

Hello Pratik,

Since the support team usually gives quick answers, but not so this time, I do hope that you didn’t read my reply as if the problem is fixed, for it is not, unfortunately.

As said, I do use the 3.2.1. Gridalicious Pro version. The 1.0.0. that you saw was only in the name of my child theme – not in the content, which is up to date, as are WordPress and Woocommerce.

The fields for username and password are displayed when using another theme (default Twenty-Sixteen for example), so the problem is not in either WordPress or Woocommerce; it looks like it is with the Gridalicous Theme.

In the Gridalicious theme, when an new customer wants to check out, the checkbox for registering a new account shows up: so that conditional works fine.
However, when the checkbox is ticked, the fields for username and password do not appear. Please see the screenshots in my first post.

Could you please look into this again and help me out? As right now, my customers will not be able to register on my site.

Thank you very much for your time!

With kind regards,
Henriët

[Henriët]

Hello Pratik,

I do have Gridalicious Pro 3.2.1. running…. the child-version was still set at version 1.0.0 though, didn’t realise I should update that as well! 🙂 Done so now!

I apologise for the confusion… Thank you for looking into it again!

Kind regards,
Henriët

[Henriët]

Hi Pratik,
Thank you for that, and you’re welcome! 🙂

Regards,
Henriët

[Henriët]

Hi Mahesh,

That is just awesome 😀 Thank you very much for this!
Went to check and see it’s already available in my WordPress dashboard too, so I can get started right away. I’m very happy and hope everything’ll work fine now, haha. Thanks ^^

Regards,
Henriët

[Henriët]

Hello Mahesh,

Thank you for your reply! That’s just my luck of course 😀

Assuming that the work will not be ready in the next week or two: is it possible to let me know what exact code I could put in my theme’s function.php? See my opening post & links there to Woocommerce docs as to what I mean.

It’ll be a workaround till you’ve been able to finish the update for compatability, but at least I’ll be able to go live with my site. Can hardly publish a site that’s still at odds and ends, can I now :).

Could you perhaps tell me as well, about when this highly-needed update can be expected?

Thanks very much again! Regards,
Henriët

[Author]

Posts