[Scott MSpectator]

i just have <!–nextpage–> in the raw content element. Nothing anywhere else or under it

[Scott MSpectator]

I just deleted it and everything near it and tried to add it again. same deal

[Scott MSpectator]

…and that code doesn’t work in a text element. What else can i try? or what might cause this?

thanks!

[Paul RModerator]

Hi Scott,

Please change your code to be <!––nextpage––> instead of <!–nextpage–>

http://theme.co/x/demo/integrity/1/shortcodes/table-of-contents/

If that doesn’t help and I don’t want to waste your time, please provide us with your login credentials so we can take a closer look? To do this, you can make a post with the following info:

– Link to your site
– WordPress Admin username / password
– FTP credentials

Don’t forget to select Set as private reply. This ensures your information is only visible to our staff.

Thanks

[Scott MSpectator]

nope nothing works now. The article you sent says to do it the way i had it in the first place so it’s contradicting what you said. Now i can’t even get it to make any changes

I don’t give out my passwords and site.

Any other ideas?

[RupokMember]

Hi Scott,

Unfortunately we can’t assist you on this without your site URL and login credentials. If you are not comfortable doing this, you may wish to consult a developer to assist you with this.

Thanks for understanding.

[Scott MSpectator]

Maybe I just need to update. In what version of cs and x theme was the bug fixed?

[Paul RModerator]

Hi Scott,

I tested this in xtheme 4.1.1 and cornerstone 1.0.6 and it works fine without issues.

Thanks

[Scott MSpectator]

Yes we know that. That’s not what I asked.

Thanks

[Scott MSpectator]

I just updated. feel free to check the hd gallery page and contact page.

thanks
easyhdtemplates.com

Also what other ways can i implement this if i’m using cornerstone. Text editor doesn’t work.

[ZeshanMember]

Hi Scott,

TOC is not fully compatible with Cornerstone. It could sometimes work when using in a Raw Content shortcode, though it might break the shortcode as in your case. I’ll forward it to our developers for further investigation. Cheers!

[Scott MSpectator]

Again, u have not answered my question about the bug fix.

Again, it is not in a table of contents right now

Again, it doesn’t work in text editor or raw content

Again, I tried all ways you provided the code.

Again, WHAT ARE THE ALTERNATIVES?

New…are u saying that the old shortcodes aren’t compatible with cornerstone?

I need the answers to all of these

What am I missing here?
Spend some time on this please.

Why do u think the dude that started this post hasn’t responded back. You don’t answer the questions or address the situations that people inquire about. You find ways to just respond quickly and be done with it. That’s not how u keep customers fellas.

[RadModerator]

Hi there,

Like what we said, TOC is not fully compatible with cornerstone or even in VC. It’s not about old or new versions, it’s the fact that <!––nextpage––> is usable only in plain content. It can’t be fully compatible for content with structures.

Here is scenario to fully explain it,

<div class="home">

content 1

<!––nextpage––>

content 2

</div>

What will happen is wordpress is going to divide it in two. Hence page 1 will have

<div class="home">

content 1

and page 2 will have,

content 2

</div>

Hence breaking the structure of HTML’s open and close elements. That of course causes malformed layout. It’s the same rule in HTML that you can’t leave an element open without closing. Then think of it what will happen on shortcode’s without open or closing too.

Hence, even if you put them in text element, it still malformed because there are other elements that wraps it, like sections.

[section]
[text]

content 1

<!––nextpage––>

content 2

[/text]
[/section]

Though, something like this should work since <!––nextpage––> is outside the section. But this is not possible with the builder and only doable on admin’s text editor.

[section]
[text]

content 1

[/text]
[/section]

<!––nextpage––>

[section]
[text]

content 2

[/text]
[/section]

We recommend <!––nextpage––> for plain contents only, or outside of any structure. I’ll forward this as feature request, but as of now, it’s not fully compatible.

Thanks for understanding.

[Scott MSpectator]

Ok thanks. A couple things were addressed there but there’s still a couple that were not addressed.

I said the code isn’t in a TOC right now. I can understand if it breaks with certain layouts

I have it as plain as it can be at the bottom of a page in its own section of CS.

Also, what other shortcodes are not compatible with CS? I need to know this because I don’t want to advertise that they work, if they cause don’t and cause issues

Thanks

[RadModerator]

Hi there,

Sorry for the confusion, but I’m not really sure what you mean by the code is isn’t in a TOC.

What we mean by TOC being incompatible, is the issues brought by combination of TOC and <!––nextpage––>. This <!––nextpage––> is a wordpress feature, it’s not dependent to anything. But TOC, to work properly, it needs to depend on <!––nextpage––>. TOC output is just a plain HTML based from the setting you set, with styling and design to represent paging created by <!––nextpage––>. Hence, TOC is for design purposes only.

Using TOC without <!––nextpage––> is useless at all. The incompatibility we’re referring is about the whole thing that’s related to to TOC, <!––nextpage––> or paging. But, TOC alone should be compatible with cornerstone or VC since it will just generate HTML, but again, useless without <!––nextpage––>.

This issue is also present to any builder that utilize <!––nextpage––>, hence proper usage and placement is required.

All X shortcodes should be compatible with cornerstone, those shortcodes are tested and intentionally made for cornerstone. <!––nextpage––> Is not from cornerstone or X theme, hence its functionality also affect TOC.

Thanks.

[Author]

Posts