Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.PageEar is correctly installed and enabled.
Now what?
The "documentation" on the webpicasso.de site isn't clear. Does it really apply to Drupal 6 users? Am I really supposed to go into the .js file and write my URL somewhere?? Is all this required before I'll actually see anything on my site, even though PageEar is enabled???
How am I supposed to put Step 6 into practice, where the user's apparently to edit the page's HTML, which is "invisible" in Drupal????
Most puzzling is why everyone else seems to "get it" and I don't....
Comments
Comment #1
dnewkerk commentedDavid, this module is pretty much plug and play. Have you gone to Administer > Site configuration > PageEar ?
It's self explanatory. I installed it on Drupal 6 to test, and had it working with my own custom images in under 1 minute.
People "get it" because they went to the module's configuration page in Drupal (almost all modules, besides those which are underlying helper modules for "other" module to use and have no user-interaction needed, add an entry to Drupal's Administer menu. Depending on the type of module (what its purpose is) it will show up in 1 of the four main categories of the menu (Content management, Site building, Site configuration, or User management)... which one is usually self-evident based on what the module "is". If it's not self-evident then ideally there is a readme.txt or install.txt to refer to.
Hint: install one of these two modules to get rapid access to the Drupal Admin menu, so you can quickly scan through it and see where things are: Drupal Administration Menu or SimpleMenu
Please, if you want people to help you, it would help to stop with the ??? and !!!!
If there is a specific issue you are having trouble with regarding the module, please mention it.
Comment #2
fitness trainer commentedKeyz,
This module certainly sounds like it's plug-n-play, but...I don't see it. I mean, it's installed and enabled (yes, from "within" Administer-->Site Configuration-->PageEar, as well as the common Administer-->Site Building-->Modules), but it ain't there. Is it supposed to be on my pages now?
Something else doesn't make sense as well...I'm thinking it's not just a module that shows up on every page, right? But I can't find a setting under Administer-->Site Configuration-->PageEar where people can specify which page(s) the PageEar should show up on.
There's no install.txt or readme.txt for this module, so I have no idea how it's supposed to work, ideally; what it's supposed to "look" like when correctly installed and enabled...very strange....
And sorry about the multiple interrogation and exclamation marks, but I am very puzzled!! It just doesn't make any sense -- my PageEar is enabled, and that's according to PageEar's own settings page under Administer-->Site Configuration-->PageEar...but...nothing! Literally, nothing!! It just really bugs me out...believe me, the multiple "????" and "!!!" don't even begin to convey the ants-in-my-pants frenzy of my mental state trying to figure out what the Dickens could possibly be up....
So anyway, my "specific issue" is that PageEar is not working for me despite being enabled, and I want to know what else I'm supposed to do. A related matter is that the "documentation" linked to by drupal.org doesn't seem to apply to Drupal users, ironically enough. Between that and the lack of a readme.txt outlining what to expect, in terms of installation and configuration, it's extremely puzzling. That's my "issue" here.
Comment #3
fitness trainer commentedKeyz,
New developments.
Turns out that I had to set, from within Administer-->Site Configuration-->PageEar-->Conditions-->Criteria, "always validate."
But I must take to task once again the sad state of "documentation," so-called, which has lead to my unnecessary befuddlement.
What was missing from official instructions was that this Condition setting needed to be set.
Still unclear is how to set things so that PageEar is only displayed on certain pages and not everywhere.
The instructions for this module are not only inadequate...they're worse even than non-existent...they're entirely misleading.
Nice module, though; don't get me wrong.
Comment #4
dnewkerk commentedIn the PageEar module itself (by default, as installed on its own) there is no Administer > Site configuration > PageEar > Conditions > Criteria, "always validate."
What happened was that you installed the optional add-on module, Condition, and didn't configure that - and as such the "condition" to display anything from PageEar was no longer present. I will grant you that the help text at the top of the page would benefit from a subtle rewording - it was perfectly clear to me, but maybe a newbie would assume it to be a "command" rather than a "suggestion". It would be better for it to say "Install the Condition module if you would like to add additional conditions...", as that would eliminate any hint of confusion.
This is your opportunity now to turn your criticisms of the documentation into action. Submit an issue to this module's issue queue, stating a suggested change to the wording of the help text. It takes no more than that - no one expects you to program anything or roll a patch or anything - just propose the exact wording of the change and why. You can also propose that a readme.txt file be added. If possible write at least some of the text you feel should be in it yourself (even if it has nothing to do with anything besides "This module does [copy and paste description from the project page]. To configure it make sure you go to Such and Such page. If you want to, you can install the _optional_ Condition module from such and such URL to further enhance this module's features." THAT is how you fix the documentation. Start the ball rolling. I expect you to do this - there's no reason not to. If you don't then eventually I or someone will. But there's absolutely no reason you can't. You say you want change - here's one simple and actionable step to begin with. Whenever you do figure something out, learn something, find a spot in documentation that ought to be reworded - do something with that knowledge. Post a feature request, bug report, whatever. This is open source. This is how it works.
I'm guessing you found this link to PageEar install instructions. The PageEar script itself is completely separate from Drupal - it's a generic JavaScript + Flash file that can be used on any website. The Drupal module for it is simply a front-end to the script that integrates it easily with Drupal. The steps for working with a module-based version of an external script are always different from the steps required to use the script in standalone HTML or within other systems.
Here's a basic walkthrough, using the "Requirement: Pages" mode of Condition module, which could also be included in the readme.txt of PageEar (in fact, please do include it):
PageEar.user/*which would display PageEar (or not display, depending on the setting) on all user profile pages, such as example.com/user/1.When ALL selected conditions are metoption, and select the PageEar condition's checkbox below. Press the "Save Configuration" button. PageEar + Conditions are now successfully configured, and PageEar should now display (or not display) on the paths you have specified.Comment #5
manfer commentedNew version 6.x-2.0 have been realeased that not depends on an external third party non GPL project and does not need any other module to manage visibility.
This instructions are no more correct.
For new version please read documentation included in realease version (README.txt, INSTALL.txt).
Comment #6
manfer commented