Jump to content
neosin

do PW v2.7 modules work with v3+?

Recommended Posts

There are lots of great looking modules that I would like to use but I am hesitant to install them purely due to the lack of visual indication that they are compatible with PW v3+. Most of the ones I want to use say they are compatible with previous versions up to 2.7 so a few questions:

  • Does this mean they are not compatible with v3 ? it would seem so since they lack the v3 tag
  • If I try them and something doesn't work and I remove them are all traces removed or can they leave artifacts behind in the DB or filesystem?

thanks in advance

Share this post


Link to post
Share on other sites

Most of them work because ProcessWire compiles them automatically.  I'd suggest you spin up a local test installation to be sure. :)

 

  • Like 1

Share this post


Link to post
Share on other sites

ok tyvm, just wanted to have confirmation before install them

 

 

Share this post


Link to post
Share on other sites
4 hours ago, neosin said:
  • If I try them and something doesn't work and I remove them are all traces removed or can they leave artifacts behind in the DB or filesystem?

 

De-installed is not quite the same as physically removed. If you de-activate a PW module, it will still be on your server. But all DB-related stuff will be removed (not every module uses the DB).

Hint: Most old modules not tagged with "PW3-compatible" can be easily enabled with adding PW3 namespaces at the very top of the php (.module) file:

<?php namespace ProcessWire;

 

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites
2 minutes ago, dragan said:

De-installed is not quite the same as physically removed. If you de-activate a PW module, it will still be on your server. But all DB-related stuff will be removed (not every module uses the DB).

Hint: Most old modules not tagged with "PW3-compatible" can be easily enabled with adding PW3 namespaces at the very top of the php (.module) file:

<?php namespace ProcessWire;

 

thank you for this tip!

much appreciated

Share this post


Link to post
Share on other sites

Very occasionally you'll come across a deprecated/removed PHP function in a very old module written for PHP 5.3 or 5.4 (what's the earliest version PW worked with years ago?) if you're now using, say, PHP 7.2. Even that kind of thing can be relatively easily Googled, or I'm sure someone on here could help with a specific problem of that kind.

Share this post


Link to post
Share on other sites

Since early 2013, when I found PW, the lowest PHP version it needs to run on is /was 5.3.8. 

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 Lmwt
      Hi there,
      I am new to PW but already very convinced. I need to build a dropdown button to browse in a collection of authors by country and language. The dropdown should be editable in the BACK and displayed on the same as the authors collection. I tried my luck with "PageField Creator" but I don't know how to display the dropdown, I simply used: 
      "$content .=$page->Land;" (the name of the select field)
      but nothing is displayed...
      I see there is a 2nd module out there to achieve this : "Select Options Fieldtype". I am not sure what is the difference, anyone has a tip?
      And a clear tutorial with the necessary steps to build this? I am a bit confused which should be the parent template or page, if it should have a file or not...
      Thanks a lot in advance!
    • By Noel Boss
      👋 PW Pros…
      I have some hooks that I need to bind at the init phase (or even __construct) and I was wondering, and I couldn't find a good and simple way to determine if I'm in the admin. Would be nice if there is a reliable short option to do so, but I can't seem to find one… Is there a coherent way to tell this no matter where I am?
      Right now, I use the following method inside one of my modules:
      public function isAdmin($page = null) { if ( strpos($this->input->url, $this->urls->admin) !== false || $this->process instanceof ProcessPageList || $this->process instanceof ProcessPageEdit || ($page instanceof Page && $page->rootParent->id == $this->config->adminRootPageID) ) { return true; } return false; } @ryan wouldn't it be nice to have something like wire()->isAdmin(); like wire()->user->isLoggedin(); to tell if we are in admin – very early on (probably even in __construct() phase of modules?
    • By benbyf
      Hi!
      Been doing some basic Twilio implementation for a client to enable them to automatically send text messages to registered users on page publish. As an upshot, I thought I would strip out the site specific work and stick up on github here: https://github.com/benbyford/TwilioChannels
      This modules pulls in the Twilio APi and enables you to send SMS messages from your front or backend.
      Send SMS message Truncate message to single message character limit Auto-select number from range of numbers depending on $To number country of origin–this enables you to send messages with a local number to that user if one added to the config. Templates usage:
      $twilio = $modules->get("TwilioChannels"); $twilio->sendSMS($toNumber, $message);  
    • By J_Szwarga
      What is the best practice for having a form (only accessible to a logged in user) save the user's progress between sections of the form? Fieldsets? Multiple forms?
      Use case: I have a very long application form that would take 30 minutes for the applicant to fill out and I would hate for all progress to be lost due to user error. The progress needs to be logged into the user's page.
      Thanks!
×
×
  • Create New...