[Not a Bug] Easy pages links

Probably not a bug, but rather intentionally.... But previous to 1.5.4 easy pages worked even if no link was enabled in any of the 3 menus. No longer, now if an easy page is not enabled in a menu the link does not work.

This is something many people, including myself do regularly to keep navigation simple, but allow the creation of page specific, topical links inside other areas of content. Such as a link to a sizing chart from specific product descriptions.

Is there an easy way to reverse this as needed or as whole if necessary?

What happens if on the TOC you click the RED icon and change it to GREEN?

same thing page not found

http://www.zen-cart.com/showthread.php?214312-Disaster!-My-Ez-pages-disappeared-after-upgrade-to-1-5-3&p=1256090#post1256090

See if this helps any. Around post #16/17

that did it thanks

But can't you see "inactive" EZ Pages simply by setting the TOC status to "On" and assigning a sort order?? SO even if It's not assigned to a menu, you can still access via a direct link?? I thought the whole purpose of this refined functionality was to give siteowners/maintainers the ability to "turn off" EZ Pages, the same way you can turn off the defined pages..

But can't you see "inactive" EZ Pages simply by setting the TOC status to "On" and assigning a sort order??
No

SO even if It's not assigned to a menu, you can still access via a direct link??
No, not without the fix above

mprough:

No

No, not without the fix above

I don't have the "fix" in place, and simply activating the TOC allows me to see this page without it being active on ANY menu:
http://clientscrappin(dot)divawebdzgn(dot)com/custom-albums-ezp-4.html

(yep this is a v1.5.4 site)

Now go to this page.. http://clientscrappin(dot)divawebdzgn(dot)com/custom-albums-ezp-56.html, and you are redirected to the home page with a message in the message stack that the page is not available..

So I'm a LOT unclear on why this "fix" is even needed..

Not to pick, but I hardly think a website with a rewrite module installed is a good example.
In any case, I have my fix and I'm not at all concerned about it =)

mprough:

Not to pick, but I hardly think a website with a rewrite module installed is a good example.
In any case, I have my fix and I'm not at all concerned about it =)

Right.. Not to pick, but I can turn off the rewrite module, and I STILL get the same result.. (and BTW, I did test both ways -- and just for giggles, I have temporarily disabled Ultimate SEO so my previous links will demonstrate this) The rewrite would have no impact on this BEHAVIOR other than to apply a pretty URL to it..

That said, I'm glad you got your fix..:smile: However, I'm simply posing the question of whether this "fix" is even needed.. The question isn't necessarily directed at you.. I'm still hoping that the folks who made this change will weigh in.. Ajeh or DrByte perhaps?? Because it's not clear to me that this "fix" is needed.. and since folks get info from this forum, I want to make sure that ALL available information is included in this discussion..

My previously posted links without Ultimate SEO on:
http://clientscrappin(dot)divawebdzgn(dot)com/index.php?main_page=page&id=4
http://clientscrappin(dot)divawebdzgn(dot)com/index.php?main_page=page&id=56

DivaVocals:

However, I'm simply posing the question of whether this "fix" is even needed.. The question isn't necessarily directed at you.. I'm still hoping that the folks who made this change will weigh in.. Ajeh or DrByte perhaps?? Because it's not clear to me that this "fix" is needed.. and since folks get info from this forum, I want to make sure that ALL available information is included in this discussion..

Why consider it a "Fix" or

Wouldn't it be more appropriate to call it a "built-in On/Off or Enable/Disable switch" that is included within a core file? It's function is pretty clearly identified in the comment adjacent to the line of code.

RixStix:

Why consider it a "Fix" or

Wouldn't it be more appropriate to call it a "built-in On/Off or Enable/Disable switch" that is included within a core file? It's function is pretty clearly identified in the comment adjacent to the line of code.

Except all this "fix" really does is to prevent one from COMPLETELY disabling an EZ Page which I think was the original Zen Cart code's actual intent.. I can turn off defined pages so that they cannot be accessed even by a link, but with this "fix" I now cannot turn off EZ Pages???

I guess I am just unclear WHY is this "fix" necessary??? Without this "fix", I can access an EZ Page in v1.5.4 which is not linked to any menu (header, footer, sidebox) via a direct link simply by turning on the TOC.. So explain to me what the ISSUE is that this "fix" is supposed to solve.. Because perhaps I am missing something here...

DivaVocals:

So explain to me what the ISSUE is that this "fix" is supposed to solve.. Because perhaps I am missing something here...

Can't say, can't debate, can't argue. All I can remember is that nothing tried had any effect until that line of code was commented.

RixStix:

Can't say, can't debate, can't argue. All I can remember is that nothing tried had any effect until that line of code was commented.Okay fair enough.. (for the record, not arguing or debating.. just merely trying to understand.:smile:)

So was your store a v1.5.4 shop?? a v1.5.3 or v1.5.2 shop?? another Zen Cart version?? Was it a migrated store?? Cause it seems this was corrected once for v1.5.3 which caused issues and requires the posted "fix" and then corrected to the behavior I am describing in v1.5.4 which doesn't require this "fix"..

I want to make sure I understand what the issue really is (if there is one) before I migrate more clients to v1.5.4.. If this is a bug, I am not seeing it, and I can't reproduce it for the 1st v1.5.4 shop I've worked on.. So again, I am just trying to understand what the REAL issue is before I blindly apply what appears IMHO to be a bandaid solution.. I am not a FAN of bandaids unless there are no other options.. I'm just not sure that this is one of those situations.. While others may have a different tolerance level for these kinds of "fixes", IMHO this doesn't "feel" like the right answer..

RixStix:

Why consider it a "Fix" or

Wouldn't it be more appropriate to call it a "built-in On/Off or Enable/Disable switch" that is included within a core file? It's function is pretty clearly identified in the comment adjacent to the line of code.

RixStix:

http://www.zen-cart.com/showthread.php?214312-Disaster!-My-Ez-pages-disappeared-after-upgrade-to-1-5-3&p=1256090#post1256090

See if this helps any. Around post #16/17

and let me be clear.. the "fix" I am referring to is the one in the post referenced previously where the "solution" to not being able to access EZ Page links directly when you have EZ Pages turned of in the header, footer, and sidebox menus is to comment out the code which REMOVES the "built-in On/Off or Enable/Disable switch".

In Zen Cart v1.5.4:
With this code left AS IS, if you turn off an EZ Page, and attempt to go to that EZ Page you are re-directed to the homepage (desirable behavior).
With this code left AS IS, if you have EZ Pages turned of in the header, footer, and sidebox menus, you can still access the page via a direct link by enabling the TOC.

DivaVocals:

Okay fair enough.. (for the record, not arguing or debating.. just merely trying to understand.:smile:)

So was your store a v1.5.4 shop?? a v1.5.3 or v1.5.2 shop?? another Zen Cart version?? Was it a migrated store?? Cause it seems this was corrected once for v1.5.3 which caused issues and requires the posted "fix" and then corrected to the behavior I am describing in v1.5.4 which doesn't require this "fix"..

I want to make sure I understand what the issue really is (if there is one) before I migrate more clients to v1.5.4.. If this is a bug, I am not seeing it, and I can't reproduce it for the 1st v1.5.4 shop I've worked on..

My eyes tend to translate allcaps into louder words than bolded text. :smile:

1.3.9h database imported into a fresh 1.5.3 install, followed by various 1.5.3 plugin installs. I just referenced the link to the 1.5.3 thread on a similar, if not the same, topic to see if it made any difference. That thread also either contains edits for a 2nd issue related to ezpages and whitepages.

RixStix:

My eyes tend to translate allcaps into louder words than bolded text. :smile:Yeah.. that's all that "interpretation" of what was MEANT versus what was SAID that folks tend to do in the forums.. Sometimes leads folks to assume emotions that aren't necessarily behind the post at all..:smile: A legitimate question (loud or NOT) is still a legit question right??:smile: I'm just trying to make sure I understand whether there is an issue here or not.. :smile:

RixStix:

1.3.9h database imported into a fresh 1.5.3 install, followed by various 1.5.3 plugin installs. I just referenced the link to the 1.5.3 thread on a similar, if not the same, topic to see if it made any difference. That thread also either contains edits for a 2nd issue related to ezpages and whitepages.Okay.. then based on my own research, and testing, this all looks like it was addressed in v1.5.4.. Meaning that the behavior for EZ Pages that I describe IS what happens in v1.5.4, but this is NOT the case in a v1.5.3 store..

Now THAT'S the information I needed to be sure I was clear on the issue.. :smile: (hence why I kept beating what may appear on the surface to be a dead horse..)

Thinking that I might look to find the way to implement the v1.5.4 handling of EZ Pages in v1.5.3 store in case I ever have a need to work on a v1.5.3 store..

SEEEEEEEEEEEEEE???? All caps doesn't mean bad things.. :smile:

. .

mprough:

In any case, I have my fix and I'm not at all concerned about it =)
I'm still not clear whether there's a case to consider that there's a bug or not.

Since this was posted in Bug Reports I'd like to get clarification: Is there a bug? If so, please explain how to reproduce using a clean unaltered install of v1.5.4, and I'll be happy to fix it.