Jump to content

Search the Community

Showing results for tags 'updates'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • Login Register Pro
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 3 results

  1. Hi, I'm new to PW and like it a lot so far. With most WordPress and Drupal websites there are frequent updates to core & plugins, some of these are security released so I tend to install any updates ASAP. When supporting many websites this update fatigue is pretty tiresome. What is your update strategy when maintaining PW sites? Would be interested to hear if you think it is valid to perhaps do a quarterly update or perhaps only even update yearly if there are no security announcements? Also just to clarify, if there a security mailing list we should subscribe to just in case an urgent fix is ever released? Thanks!
  2. I'd personally be very interested in a module that allows me to check for updates of my existing modules and update them indiviidually or in a group. I'm not referring to updates within a directory but rather performing a check against the module directory here. A simple button to click that would then list the differences between available and what I have would be ideal. Just a thought but I can see it adding value for sure.
  3. If you get a compile error (Error 500) when updating a module (for example with the ModuesManager), this could be for a likely but not so obvious reason. I want to share this. Example alert (Maintenance Module update example): Compile Error: Cannot redeclare class MaintenanceMode (line 3 of /.../site/modules/MaintenanceMode/MaintenanceMode.module) This looks like an attempt to declare the same module class twice. What had happened here was this: When dragging a module over an ftp client to the modules folder, it got placed inadvertedly into another module folder and not in the modules root. - So the module became "invisible" (hidden) on your ftp client at first glance. The funny thing was that the misplaced module was still working alright. No alarm bells rang. Trouble came after we tried to update the module (by ftp or by the modules manager) months later. Then the infamous error 500 appeared. So, before wasting time looking closely at database entries and module codes, maybe check first whether there is a duplicate of the updated module buried in the modules folder somewhere.
×
×
  • Create New...