Virtual Forum Tour

[₪» ⅀ ƪ Ƒ «₪]

Brian pardon me if this has been asked - this is only for the homepage, right? I can't have it take you to certain threads or boards or anything as part of the tour itself, just keep it on the homepage?

[Brian]

Apr 20, 2018 11:44:17 GMT -8 ₪» ⅀ ƪ Ƒ «₪ said:

Brian pardon me if this has been asked - this is only for the homepage, right? I can't have it take you to certain threads or boards or anything as part of the tour itself, just keep it on the homepage?

It works globally. That's why there's a landmark URL option.

[₪» ⅀ ƪ Ƒ «₪]

Apr 20, 2018 11:57:33 GMT -8 Brian said:

Apr 20, 2018 11:44:17 GMT -8 ₪» ⅀ ƪ Ƒ «₪ said:

Brian pardon me if this has been asked - this is only for the homepage, right? I can't have it take you to certain threads or boards or anything as part of the tour itself, just keep it on the homepage?

It works globally. That's why there's a landmark URL option.

Ahhh ohkay I will have to dig further into this plugin, then, thank you for your response

[irontongue]

Hi. It's me again.

I really like this idea and would love to incorporate this but, It might be a little more than what I can comprehend.

I'm using the Sidebar Redux plugin. Is there a way to make this target different sidebar boxes, and widget boxes on a custom pages?

I'm pretty lost and I might give up at any time. LOL



But, I think this would help my members get better acquainted with the site.

-Iron Tongue

[Brian]

Mar 28, 2019 4:31:11 GMT -8 irontongue said:

I'm using the Sidebar Redux plugin. Is there a way to make this target different sidebar boxes

You can fill out the ID field for sidebar containers you want to target in the Sidebar Redux plugin's settings which should allow you to target them individually. Remember that an ID can only consist of alphanumeric characters (A to Z, lowercase a to z, and numbers 0 to 9), hyphens (-), and underscores (_). No two elements should share the same ID.

Mar 28, 2019 4:31:11 GMT -8 irontongue said:

and widget boxes on a custom pages?

Each widget you add to a custom page has a unique ID generated for it that gets assigned to its associated elements on the page. When viewing the custom page you can right-click one of your widgets and select Inspect Element (or whatever your browser's equivalent is) to see its underlying HTML. Somewhere up the tree should be an element with an ID, like the highlighted one my cursor is pointing at in the screenshot below.

dev.prbrds.com/b/o/TcbkKUoPH0sdPJjmahNN.png

If you want to make sure it's the correct element you can move your mouse cursor over the HTML tag like I've done in the screenshot. It'll highlight the element on the page above the console.

[irontongue]

Mar 28, 2019 8:55:16 GMT -8 Brian said:

Mar 28, 2019 4:31:11 GMT -8 irontongue said:

I'm using the Sidebar Redux plugin. Is there a way to make this target different sidebar boxes

You can fill out the ID field for sidebar containers you want to target in the Sidebar Redux plugin's settings which should allow you to target them individually. Remember that an ID can only consist of alphanumeric characters (A to Z, lowercase a to z, and numbers 0 to 9), hyphens (-), and underscores (_). No two elements should share the same ID.

Mar 28, 2019 4:31:11 GMT -8 irontongue said:

and widget boxes on a custom pages?

Each widget you add to a custom page has a unique ID generated for it that gets assigned to its associated elements on the page. When viewing the custom page you can right-click one of your widgets and select Inspect Element (or whatever your browser's equivalent is) to see its underlying HTML. Somewhere up the tree should be an element with an ID, like the highlighted one my cursor is pointing at in the screenshot below.

dev.prbrds.com/b/o/TcbkKUoPH0sdPJjmahNN.png

If you want to make sure it's the correct element you can move your mouse cursor over the HTML tag like I've done in the screenshot. It'll highlight the element on the page above the console.

Sweet, I'll try to figure this out when I get home.

[irontongue]

Brian ,

I got it going, thanks!

This is an awesome plug in!

Should help my members tremendously.

If I have any other questions I'll post back.

Thanks again for the great plug in and getting me pointed in the right direction.

[Sammiie]

Brian

I seem to have run into an issue that's completely stumping me... because no matter what, I can't figure out what's going wrong???

My plugin back-end stuff seems to  look fine, but the tour stops after ID # 14, skips a step, and directs to the wrong page, despite that page not being linked until two steps ahead.

I've checked and double-checked with my code, the plugin stuff, and I can't figure out why only that one​ is giving me grief.

My forum is here. You'll find the tour here.​​​

ID 15 and onward aren't popping up after this issue. When running the tour, you get to point 14, then click the next arrow, the page redirects, dims a bit, and nothing. In the page URL, the ID still says 14, but redirects to point 16 and is completely skipping point 15, despite not supposing to be directed to anything. 

[Brian]

Apr 14, 2019 5:09:22 GMT -8 Sammiie said:

ID 15 and onward aren't popping up after this issue. When running the tour, you get to point 14, then click the next arrow, the page redirects, dims a bit, and nothing. In the page URL, the ID still says 14, but redirects to point 16 and is completely skipping point 15, despite not supposing to be directed to anything. 

The number in the URL doesn't represent the ID you give the tour landmarks. It just represents the index of the landmark it's on starting from 0 which represents the first landmark in that tour.

Two things are happening here:

• Landmark ID 15 isn't included at all in the list of landmarks in the Tours tab, so when the URL says tourstart=14 index 14 represents the 15th landmark in your tour, which is landmark ID 16.
• The CSS selector being targeted by landmark ID 16 (and many more landmarks following it) is .pagneame which appears to be a typo as it doesn't match any elements on the page, breaking the tour as expected.

[Sammiie]

Apr 15, 2019 9:06:25 GMT -8 Brian said:

Apr 14, 2019 5:09:22 GMT -8 Sammiie said:

ID 15 and onward aren't popping up after this issue. When running the tour, you get to point 14, then click the next arrow, the page redirects, dims a bit, and nothing. In the page URL, the ID still says 14, but redirects to point 16 and is completely skipping point 15, despite not supposing to be directed to anything. 

The number in the URL doesn't represent the ID you give the tour landmarks. It just represents the index of the landmark it's on starting from 0 which represents the first landmark in that tour.

Two things are happening here:

• Landmark ID 15 isn't included at all in the list of landmarks in the Tours tab, so when the URL says tourstart=14 index 14 represents the 15th landmark in your tour, which is landmark ID 16.
• 
  
• The CSS selector being targeted by landmark ID 16 (and many more landmarks following it) is .pagneame which appears to be a typo as it doesn't match any elements on the page, breaking the tour as expected.

.pagename does exist... on a different page. The problem is that the tour is skipping a whole item, redirecting to the wrong page, and breaking. Everything I have in the back-end seems to check out... as I have a similar item like this earlier in the tour that works fine.


The red circled one is the one that's not popping up at all. As you can see, there is no ".pagename" listed for that one; it is​ listed for the one following it, but not the one that's not showing up. For this particular step, I just want a box to pop up with no particular anchor. "Body" seemed to work for the other similar boxes, but for whatever reason, this one is not.​​​

[Kitty Katt]

Sammiie,

I think Brian was pointing out (and also noticeable in your image) that ".pagename" is misspelled in some places. From your image, ID #17 and ID #18 both have it misspelled as ".pagneame" - with the "n" and first "e" switched. Perhaps there are other instances of it being misspelled above that?

My apologies, Brian, if I have overstepped here.

[Brian]

Apr 16, 2019 3:40:15 GMT -8 Sammiie said:

.pagename does exist... on a different page.

Yes, .pagename does indeed exist. But that's not what you've specified for most of them. It appears that .pagneame was typed into the settings instead of .pagename.

Apr 16, 2019 3:40:15 GMT -8 Sammiie said:

The problem is that the tour is skipping a whole item, redirecting to the wrong page, and breaking.

As I mentioned before that item is very much absent from your list of landmark IDs and is thus not included in the tour.

[Sammiie]

Brian

oh, oop. I failed to notice the typos. Thanks to the both of you for spelling that out for me!

Ok, so fixing those, fixed the tour..... but it's still skipping item # 15. Can you give me some insight on that? 

[Brian]

Apr 16, 2019 22:08:36 GMT -8 Sammiie said:

Brian

oh, oop. I failed to notice the typos. Thanks to the both of you for spelling that out for me!

Ok, so fixing those, fixed the tour..... but it's still skipping item # 15. Can you give me some insight on that? 

Read my posts again very carefully.