Jump to content
adrian

Page Protector

Recommended Posts

@ottogal - I just tested here to confirm it is still working as expected with PW 3 and everything seems to be fine. Unfortunately I am traveling at the moment with very limited internet access so I don't really have much time to help you at the moment. Is it possible you also have some other modules that are impacting access permissions? I would try testing on a clean PW install to see if you can narrow down the issue.

I'll check back in again when I can to see where you're at.

Share this post


Link to post
Share on other sites

@adrian: Thank you for your time, anyway.

At the moment I don't have the time to dig deeper into it, but surely will try later.

Share this post


Link to post
Share on other sites

On the Settings page of the module PageProtector 0.1.4 the "Protect Entire Site" shortcut is missing.
Was it removed intentionally?

Share this post


Link to post
Share on other sites

It's still there for me. Remember this will only be on the main module config settings page, not the settings tabs for individual pages.

Also, note that once you have protected the homepage, this shortcut is no longer available - it doesn't have any purpose in this case.

post-985-0-55478100-1458177940_thumb.png

Share this post


Link to post
Share on other sites

once you have protected the homepage, this shortcut is no longer available - it doesn't have any purpose in this case.

I understand. But then the hint under Instructions ("... or use the "Protect Entire Site" shortcut below") should be removed in this case, too.

Share this post


Link to post
Share on other sites

I have to overwrite the default Prohibited Message in each individual page Setting. I'm missing the possibility to do it in the module's Settings for all ptotected pages.

Share this post


Link to post
Share on other sites

Hi @ottogal,

I have just committed a new version which handles both your requests:

  • hiding the instructions about the shortcut to protecting the entire site
  • ability to set a default Prohibited Message in the module's config settings.

Let me know if you have any problems with this.

  • Like 4

Share this post


Link to post
Share on other sites

Hi @adrian,

sorry for the late reply.

I tried to install the new version 0.1.5 from the Backend via Modules > Site. Despite the notification of the successful installation, the module was not upgraded.

(I'm running PW 3.0.15).

Share this post


Link to post
Share on other sites

Hi @adrian,

sorry for the late reply.

I tried to install the new version 0.1.5 from the Backend via Modules > Site. Despite the notification of the successful installation, the module was not upgraded.

(I'm running PW 3.0.15).

This sounds like a modules caching issue or maybe a FileCompiler caching issue? Can you try a Modules > Refresh? I'd be surprised if that doesn't work, but if not, maybe clear your FileCompiler cache as well? 

Share this post


Link to post
Share on other sites

Did both, same result: If I click "Continue to module settings" (below the "updated successfully" message), the settings show the 0.1.4 version.

Share this post


Link to post
Share on other sites

Did both, same result: If I click "Continue to module settings" (below the "updated successfully" message), the settings show the 0.1.4 version.

I am not sure what to suggest. Can you take a look in the .module file and make sure it says: "15" as the version number?

If it does, then can you let me know if the new functionality is available despite the version number in the module config showing 14?

Share this post


Link to post
Share on other sites

Hhm, getModuleInfo() returns  'version' => 15, and all the files have the date of yesterday (my update). Obviously the update process was successful.

But the entry on Modules > Site continues to display 0.1.4, the settings page is the old one. The new functionality is not available...

Should I try to uninstall and reinstall the module, instead of updating?
 

Share this post


Link to post
Share on other sites
Should I try to uninstall and reinstall the module, instead of updating?

Sure, although if you have lots of separate pages protected you might want to copy the module settings from the modules DB table so you can add them back in without having to re-create them all after the reinstall.

Are you having issues with updating any other modules, or just this one?

Share this post


Link to post
Share on other sites
Are you having issues with updating any other modules, or just this one?

My other modules all are up-to-date, so I can't say.

copy the module settings from the modules DB table

Thank you for the idea!

Uninstalling and reinstalling the module solved the issue. (Before the reinstall I had to delete the files in the modules folder.) Many thank, adrian!

Share this post


Link to post
Share on other sites

I crowed too soon: After a new start of the backend I made a modules refresh to find the following "success" message (green):

  • Session: Cleared the admin theme navigation cache (topnav)

  • Session: Detected 1 module version change (will be applied the next time each module is loaded):

    PageProtector: 0.1.5 => 0.1.4
  • Session: Modules cache refreshed (112 modules)

  • Session: Module "FieldtypeEvents" has multiple files (bold file is the one in use). Click here to change which file is used

    /site/modules/FieldtypeEvents/FieldtypeEvents.module/site/modules/FieldtypeEvents-master/FieldtypeEvents.module
  • Session: Module "ImportPagesCSV" has multiple files (bold file is the one in use). Click here to change which file is used

    /site/modules/ImportPagesCSV-master/ImportPagesCSV.module/site/modules/ImportPagesCSV/ImportPagesCSV.module
  • Session: Module "InputfieldEvents" has multiple files (bold file is the one in use). Click here to change which file is used

    /site/modules/FieldtypeEvents/InputfieldEvents.module/site/modules/FieldtypeEvents-master/InputfieldEvents.module
  • Modules: Upgrading module (PageProtector: 0.1.5 => 0.1.4)

And the installed version is again 0.1.4 ...   :(

(By the way: In the case of multiple files for a module, one with the trailing "-master" and one without it, which one should I use? What's the difference?)

Share this post


Link to post
Share on other sites

Any chance you can PM me with access to this server, or is it a local dev setup?

Why do you have multiple copies of so many of your modules?

You should delete all the -master versions.

Also, when installing modules I would recommend the core method of installing by class name - it looks to me like you installed several modules manually and then used the upgrades modules to upgrade them - hence the extra copies. You must have a 0.1.4 version of PageProtector somewhere in your system.

Share this post


Link to post
Share on other sites

Now I installed the module via github, that worked without issues.

At the moment I can't give you access to the setup.

Thanks for the hints to the -master versions of modules. Again the question: What are they for, what's the difference to the others?

  • Like 1

Share this post


Link to post
Share on other sites

The -master issue is probably just a result of you manually unzipping and FTP'ing the module folder. If you use the modules page to install, either via class name, github url, or from your hdd you won't see these. 

PS Glad you are now seeing 0.1.5!

Share this post


Link to post
Share on other sites

Because when you manually unzip a project from Github it has "-master" or "-dev" etc in the folder name. You don't want this in PW, so you either need to manually remove this, or install automatically from the zip itself. If you install manually and then run the Upgrade module, it is adding the version without the -master so you end up with two versions. Does that explain it?

Share this post


Link to post
Share on other sites

Yep. :)  - As far as I see both versions of the module file are identical; so for a installed module of which I've got only the -master version, I can rename the file pruning the trailing "-master"?

Share this post


Link to post
Share on other sites

Yep. :)  - As far as I see both versions of the module file are identical; so for a installed module of which I've got only the -master version, I can rename the file pruning the trailing "-master"?

Yes that would be preferable.

Share this post


Link to post
Share on other sites

Thank you for all your explanations (and your great modules!)...

Share this post


Link to post
Share on other sites

Me:

As far as I see both versions of the module file are identical; so for a installed module of which I've got only the -master version, I can rename the file pruning the trailing "-master"?

You:

Yes that would be preferable.

That seems to be a bad idea:

When I removed the trailing  -master  from the folder's name  \site\modules\PageTableExtended-master  and tried to login, I got this Warning:

Field: Fieldtype 'FieldtypePageTableExtended' does not exist

With pruning the  -master  from  \site\modules\MarkupSimpleNavigation-master , I got an "non object" error message refering to the line where the navigation is rendered...

So I renamed back all these folders to their previous names (with trailing  -master). 

???

Share this post


Link to post
Share on other sites
That seems to be a bad idea:

Just make sure you run Modules > Refresh after renaming and they will work again.

The reason I think it's important is so that you can use the Upgrades module to upgrade all your modules to new versions easily. And in future if you install using the ClassName or the zip (via URL or upload), then you won't ever have to deal with the "-master".

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="optin" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="optin" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: PrivacyWire Git Repo
      Download as .zip
      I would love to hear your feedback 🙂
      CHANGELOG
      0.0.5 Multi-language support included completely (also in TextFormatter). Added possibility to async load other assets (e.g. <img type="optin" data-category="marketing" data-src="https://via.placeholder.com/300x300">) 0.0.4 Added possibility to add an imprint link to the banner 0.0.3 Multi-language support for module config (still in development) 0.0.2 First release 0.0.1 Early development
    • By MoritzLost
      This is a new module that provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Beta release
      Note that I consider this a Beta release. Since the module is relatively aggressive in deleting some caches, I would advise you to install in on a test environment before using it on a live site.
      Let me know if you're getting any errors, have trouble using the module or if you have suggestions for improvement!
      In particular, can someone let me know if this module causes any problems with the ProCache module? I don't own or use it, so I can't check. As far as I can tell, ProCache uses a folder inside the cache directory to cache static pages, so my module should be able to clear the ProCache site cache as well, I'd appreciate it if someone can test that for me.
      Future plans
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory

    • By David Karich
      Admin Page Tree Multiple Sorting
      ClassName: ProcessPageListMultipleSorting
      Extend the ordinary sort of children of a template in the admin page tree with multiple properties. For each template, you can define your own rule. Write each template (template-name) in a row, followed by a colon and then the additional field names for sorting.
      Example: All children of the template "blog" to be sorted in descending order according to the date of creation, then descending by modification date, and then by title. Type:
      blog: -created, -modified, title  Installation
      Copy the files for this module to /site/modules/ProcessPageListMultipleSorting/ In admin: Modules > Check for new modules. Install Module "Admin Page Tree Multible Sorting". Alternative in ProcessWire 2.4+
      Login to ProcessWire backend and go to Modules Click tab "New" and enter Module Class Name: "ProcessPageListMultipleSorting" Click "Download and Install"   Compatibility   I have currently tested the module only under PW 2.6+, but think that it works on older versions too. Maybe someone can give a feedback.     Download   PW-Repo: http://modules.processwire.com/modules/process-page-list-multiple-sorting/ GitHub: https://github.com/FlipZoomMedia/Processwire-ProcessPageListMultipleSorting     I hope someone can use the module. Have fun and best regards, David
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "https://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


×
×
  • Create New...