evita

Thank you, @sophiegy ! This worked! I cannot believe I missed this!!!

Hi @karolmanijak,

thanks for getting back to me and apologies for the delay responding. I’ve been away.

Let me rephrase what I’m trying to achieve: I want a custom Front Page where the layout of the main content area (the middle column) takes the full width of the screen, just like in the theme demo. I’ve tried many different things, including your suggestion in #1. I also created a new custom Front Page that is based in the default Front Page (the blog Home), or, alternatively, copied the style of that middle column in the blog Home, but do not manage to achieve the full width. The only thing that works is changing the default width for the entire theme, which I do not want.

These are the Front Page template blocks:

https://photos.app.goo.gl/Y2DXRZL9DGN6STZE9

And here is the backend of the page that is set as homepage:

https://photos.app.goo.gl/xbYdU3jTrjCBzsCL7

This is how it looks on the frontend:

https://photos.app.goo.gl/UtBqpxRS41fncq178

And this is how I’d like it to look, at least in terms of content width which I achieved by editing the page template layout from 720 px to 1500 px:

https://photos.app.goo.gl/PP8cpMmXiJiLR7yR6

The problem is: this changes the layout of the entire website!

(This is all on my localhost, hence I’m not posting any links to a live site).

I hope this helps!

PS: uploading images via link is not working (!), hence I’m posting the links to the photos.

• This reply was modified 1 year, 8 months ago by evita.

I tried #1 by editing a test post on the code editor :

<ol>
  <li>This is the first item.
    <!-- wp:footnote -->
    <p>This is your footnote content for item 1.</p>
    <!-- /wp:footnote -->
  </li>
  <li>This is the second item.</li>
  <li>This is the third item.</li>
</ol>

… and I get this message in the visual editor:

Your site doesn’t include support for the “core/footnote” block. You can leave it as-is, convert it to custom HTML, or remove it.

How should I implement it?

As a side note, when I manually add the footnote block I see that there’s a lot more going on in the code:

<sup data-fn="652a5e8c-3be6-437d-b170-9068ce035379" class="fn"><a href="#652a5e8c-3be6-437d-b170-9068ce035379" id="652a5e8c-3be6-437d-b170-9068ce035379-link">1</a></sup>
	<a href="#652a5e8c-3be6-437d-b170-9068ce035379" id="652a5e8c-3be6-437d-b170-9068ce035379-link">1</a>
</sup>

… and then further down:

ol class="wp-block-footnotes"><li id="652a5e8c-3be6-437d-b170-9068ce035379">Footnote text. <a href="#652a5e8c-3be6-437d-b170-9068ce035379-link" aria-label="Jump to footnote reference 1">↩︎</a></li></ol>

# 2 – This is what I was trying to avoid with this setup if possible…

@threadi – tried that, but it didn’t work with me.

@hcabrera – Eureka! It’s working now!! :-)) I wonder what might have disabled it?!!

Here is the file. It’s located in C:\MAMP\conf\apache\httpd.conf, which is its default location per this page.

There is an additional httpd.conf located in C:\MAMP\conf\apache\original\httpd.conf. I don’t know if that’s relevant but here is a side by side comparison of the two files.

Thanks for taking a look!

Hi @threadi – That page is also showing a 404…

Anything else I should do?

As I explained in an earlier post, I was trying to filter content (custom post types) from a query loop. Just that.

From your plugin page:

Key features

• Filters any post types
• Supports any filtering criteria
• Easy integration on a page using Widgets or Shortcodes