Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by louisstephens

  1. I was just curious if anyone has tried installing this lately and ran into any problems regarding "Module requirements are not fulfilled so installing may cause problems."..  The module page lists that the required versions is >= 3.0.62 but when I go to install the module it is saying >= 3.0.210 is required. I am currently running 3.0.98 and if I go through with the install I get a warning regarding that I am not meeting the processwire requirements. It seems to install just fine, but I was just worried of creating other issues if I proceeded.

  2. Thanks everyone! I think I missed a few tweaks I had done in my previous .htaccess file when I replaced it. If my memory serves me correct, I never really had an issue upgrading in the past.

    As far as the "Upgrades" module, I do have it installed, but when I tried to go down this route I kept running into errors. It would download the necessary files (htaccess, config, and wire) but then error out on my me regarding the admin "theme". I just checked my logs and cant find the specific error that I got, but it had something to do with the "admin theme" and FieldTypeTextAreas. I know it isnt a lot to go on, but I will keep digging through my logs.

    The one that does keep popping up in the logs is:

    2023-10-11 16:35:41 guest https://demo.com/processwire/login/ Fatal Error: Uncaught Error: Class 'FieldtypeTextarea' not found in /mnt/stor17-wc1-ord1/949814/demo.com/web/content/site/modules/FieldtypeTextareas/FieldtypeTextareas.module:20 Stack trace: #0 /mnt/stor17-wc1-ord1/949814/demo.com/web/content/wire/core/ModulesFiles.php(324): include_once() #1 /mnt/stor17-wc1-ord1/949814/demo.com/web/content/wire/core/ModulesLoader.php(723): ProcessWire\ModulesFiles->includeModuleFile('/mnt/stor17-wc1...', 'FieldtypeTextar...') #2 /mnt/stor17-wc1-ord1/949814/demo.com/web/content/wire/core/Modules.php(667): ProcessWire\ModulesLoader->includeModule(Object(ProcessWire\ModulePlaceholder), '') #3 /mnt/stor17-wc1-ord1/949814/demo.com/web/content/wire/core/WireClassLoader.php(283): ProcessWire\Modules->includeModule('FieldtypeTextar...') #4 [internal function]: ProcessWire\WireClassLoader->loadClass('ProcessWire\\Fie...') #5 [internal function]: spl_autoload_call('ProcessWire\\Fie...') #6 /mnt/stor17-wc1-ord1/949814/demo.com/web/content/ (line 20 of /mnt/stor17-wc1-ord1/949814/demo.com/web/content/site/modules/FieldtypeTextareas/FieldtypeTextareas.module)
  3. We have a Processwire (3.0.98) project that has been happily trundling along for around 4 years (give or take) without fail. I have tried to stay on top of maintenance and upgrades over the years, but some other projects got in the way and it got a bit neglected. I got the itch to upgrade the textarea yesterday (for a new template), so I went down the path of updating processwire.

    • I downloaded the latest stable version 3.0.229
    • Renamed the index, htaccess.txt, and wire folder to new_*
    • Uploaded the new files via ftp
    • Renamed the old index, htaccess, and folder to start with .HOLD. (just in case)
    • Renamed the new files to take their place

    When I went to refresh the site, I just got a 500 server error, and unfortunately setting config->debug to true didnt show any helpful information. I am sure I am making quite a large jump in versions, but have I happened to miss something in the update process? I thought I would be fine since I was still in version 3.x.x territory. 

  4. I have been avoiding developing this section of our website for a day now as it looks horrendous in my opinion. The general layout of the section is to have our 4 main services with their titles on the left hand side. When you click on one, an entire blocks swings in from the top (animate.css) with the title, brief snippet, cta, and a youtube video "explaining" the service with plenty of buzz words. The entire section is quite tall and the video sticks out like a sore thumb.  I have been racking my brain on perhaps a "better solution", but I am all out of ideas. I was tasked to revamp the site (was on processwire, now in gridsome/graphcms just to try out something new), but the mockup is a bit out of date (just feels old tech for a marketing agency). Thankfully, I have a bit of wiggle room to make changes, as long as I can show something interesting.

    I was just wanting to hear some of your feedback/ideas on how you would go about tackling this section to make it feel a bit more interesting/clean. I have included a very basic "mockup" of the section in question (left = service titles | right = content regarding service => title, snippet, cta, video). The section is also the full width of the browser, so in my dev enviornment atm it is 1825px x 850px.


  5. Sure thing! Here you go:

    var gulp = require("gulp");
    var sass = require("gulp-sass");
    var browserSync = require("browser-sync").create();
    var autoprefixer = require("autoprefixer");
    var rename = require("gulp-rename");
    var cssnano = require("cssnano");
    var postcss = require("gulp-postcss");
    var minify = require("gulp-minify");
    //var bourbon = require("bourbon").includePaths;
    //var neat = require("bourbon-neat").includePaths;
    // Put this after including our dependencies
    var paths = {
    styles: {
        // By using styles/**/*.sass we're telling gulp to check all folders for any sass file
            src: "./src/scss/*.scss",
        // Compiled files will end up in whichever folder it's found in (partials are not compiled)
            dest: "./dist/css/"
    },php: {
            src: './*.html',
    scripts: {
        src: "./src/js/*.js",
        dest: "./dist/js/"
    // Easily add additional paths
    // ,html: {
    //  src: '...',
    //  dest: '...'
    // }
    function style() {
        return gulp
            .pipe(sass({ outputStyle: "expanded" }))
        .pipe(rename({ suffix: ".min" }))
            .pipe(postcss([autoprefixer({ browsers: ['> 1%', 'last 3 versions', 'Firefox >= 20', 'iOS >=7'] }), cssnano()]))
    exports.style = style;
    function php() {
        return gulp
    exports.php = php;
    function script() {
        return gulp
        .pipe(minify({noSource: true}))
        .pipe(rename({ suffix: ".min" }))
    exports.script = script;
    function watch() {
          // You can tell browserSync to use this directory and serve it as a mini-server
          port: 8181,
            proxy: "http://localhost:8888/project-folder/"
          // If you are already serving your website locally using something like apache
          // You can use the proxy setting to proxy that instead
          // proxy: "yourlocal.dev"
        //I usually run the compile task when the watch task starts as well
        gulp.watch(paths.styles.src, style);
        gulp.watch(paths.scripts.src, script);
        gulp.watch(paths.php.src, php);
    exports.watch = watch


    • Like 2
  6. 13 hours ago, OrganizedFellow said:

    I never could get that to work reliably. Never figured out why.


    To be honest, it also took me a while to get it all working. Apparently I started using it with an outdated syntax of gulp (1 version behind) and when I went to add some new node modules, everything just blew up in my face. 

    If you are interested, I would be more than happy to share my gulp file with you or anyone.

  7. I use gulp with browser-sync in my current workflow. I really like it as I can specify what files extensions (php, css, etc etc) to watch for changes and once it detects a file change, it automatically reloads the page. I also will be using gulp-cache for cache busting (for changes with my scss/css). So far I have been very happy with the results.


    • Like 1
  8. Is the title and menu bar contained within a wrapping div? You could do this for the individual elements, but have you tried bumping up the z-index of the wrapping div or the ind. elements to bring them on top of the background image.

    • Like 1
  9. After a whiIe of not using the module I recently ran into an issue when I reinstalled the hanna code module. I tried uninstalling the module and reinstalling it, but then I run into the issue of:

    SQLSTATE[HY000]: General error: 1813 Tablespace '`revamp`.`hanna_code`' exists.

    I checked the database with adminer and searched for "hanna_code", but I am not seeing any tablespace in the database. Is there a way of clearing this out so I can do a fresh install?

    Also, I was going to use this module to allow people to define the form fields they would like to use in a setup I am currently developing (one per line). For example, they could type in [[form-firstname]] and the output would be:

    <input type="text" name="firstname" id="firstname" required>
    <label for="firstname" class="is-required">First Name</label>

    In my infinite wisdom, I thought I could explode by the line and wrap each input into a column/row. Obviously this doesnt work as the output is actually two lines (and some of my hanna codes would output up to 6 lines). Is there a good way to go about adding in rows/columns to the actual inputs?

  10. I wasn't quite sure where to put this as this not really a firm question but more of a discussion (if this needs to be moved, I do apologize). I am remaking an internal app for work and most of the users log into the admin to create pages etc etc. With the old app, I have noticed a lot of unpublished pages, duplicated pages, abuse of the system (my fault as I didn't do anything to set guidelines of maintenance etc etc) and was wondering how some of you "post" notes for the  user.

    I was going to send out an automated email once I create their user account with all of useful documentation, but I feel that they will either read it once and delete it or just skip right over it. In my mind it would be nice to have a place where this information was always available, but I have a feeling that it would just be ignored after a while. Unfortunately, I dont have the time to watch the backend like a hawk for any wrong doings, but lately the old app has become the unlawful wild wild west (the page tree is getting out of hand).

  11. Unfortunately, I do not believe the pagination has yet made it to repeater fields yet. There was a blog post made in 2016 regarding it, and I believe it is only possible with the Profields Table field atm (though the blog mentions the possibility of adding it in the future). I am sure other items were deemed more important, and pushed repeater pagination down the line. 

    I have read that AJAX loading repeaters might help, though it is the default setting. 

    • Like 1
  12. I actually was working on something similar to import/exporting using the Rest API module here at work. I have a cron job set up targeting a specific page (on the live site) with some jquery checking the api endpoint (local dev server with an external locked ip). I then post that to the targeted page and run some php to update fields on the live site with the content.. It's overkill, but I like it as it allows new content/changes to be uploaded if in case I wasnt able to get to it.

    • Like 1
  13. So I ran into a very strange issue today. I have a template with a pagetable and I went to add an item to it, when I went to select an image (for an image field) the page instantly threw up an error

    "ProcessPageSearchLive: No search specified"

    The page's content also switched to the image attached. This all worked perfectly last week (local mamp box). Has anyone experienced this before, and how did you solve it?



  • Create New...