modifiedcontent

Issue 1: Why do I get lots of random Russian (?) text when I try to look up addresses? And the location search results are awful; the system suggests random street addresses (with lots of Russian) when you type in something basic like 'London, England'. Full addresses seem to work better, but only without postal codes - 'nothing found' when you try to search with postal codes included. Issue 2: Maps show up in the admin area, but not on the front-end. I have another version of the same site where they do show up on the front-end without problems, so am a bit puzzled where the problem could be. What are typical causes I could check? Edit: The problem with the map not showing up on the front end (Issue 2) had something to do with this error showing up in Chrome Inspect/DevTools: Uncaught TypeError: $ is not a function at (index):529 Something with jQuery. The error disappeared when I copied module files from another site where Leaflet Map did work. Not sure where the cause of the error is exactly.

Thanks for response Pip. The template's name is 'event' and I just create the usual way via admin, Add New etc. It's probably something dumb in my particular templates. I may have old code/configuration somewhere that does something with the slug creation. Can't find where. Edit: Nevermind. I found it. In the parent template 'events' under Family there was a 'name format for children' defined. Also 'allowed template(s) for children' was not set - weird that page creation was possible at all...

@j__ , did you ever figure out what caused this?

Annoying small problem; when I create pages for a certain type/template, they initially get created with the slug /untitled and empty title and name fields on the next page. I have to enter the title and slug again to create the page. Has anyone seen that before? Why does it happen and how can I fix it? Same issue reported here, with no solution.

I had a simple 'Delete My Account' link for users in my site that used to work fine, with a function like this: But it no longer works, after upgrades I guess. I get a fatal server error: cannot be deleted: it is the current page being viewed, try $pages->trash() instead Or when I use trash(), I get: Exception: This page (id=XXXX) may not be placed in the trash That error is thrown in core/PagesTrash.php by a check for isDeleteable(). I can't find info what makes a page 'deleteable' or not. What is now the recommended way to do this?

Has anyone else seen front-end editing not working on certain pages? When I try to make an edit and click Save, I get a javascript pop-up with 'No changes to save'. Anyone have any idea what causes this? Javascript conflict maybe?

Did anyone ever find out how to solve this? Or at least make that error disappear... Edit: Just switched from Reno admin theme to UIkit. I think the error message is now gone.

A few more points to watch out for. You need to copy the Authentication Salt in config.php to be able to use your login from the old database: /** * Installer: User Authentication Salt * * Must be retained if you migrate your site from one server to another * */ Installed modules and customizations can also mess up things. After simply uploading my backed-up /site folder into the new installation, I got a scary fatal server error. To step back I restored the /site folder of the fresh installation. I had replaced the fresh install database with my original backed-up database. That worked fine. I see all my old content and templates etc. in the admin area. Next I have uploaded all modules from the backed-up /site/modules to the new installation /site/modules. In the back-end I have clicked Refresh in Modules. It finds the modules and installs them. You may have to repeat Refresh a few times. I still keep getting this error: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'field_headshot.filedata' in 'field list' After uploading the rest of the backed-up /site folder, everything else seems to work fine.

Cool! Looking forward to trying this. Thanks gebeer

Another dumb question; what am I supposed to do with the following in config.php: I have tried uncommenting '@var Config $config', but that breaks stuff. And what is '@var bool'?

Is there no quick way in Processwire to just clear all caches in one go? I keep running into caching problems and then have to turn on/off caching per templates. I have also read that you can delete the contents of the cache folder, but think it broke my site the last time I tried that. I am now troubleshooting another issue that may or may not have anything to do with caching. It would just be nice if I could just eliminate that as a cause, but wouldn't even know which template/cache to try to clear.

Excellent. Thanks rick and wbmnfktr. I'll do this in the coming weeks and will report back.

What is currently the best way to move a Processwire site to a new server? I have to upgrade my VPS, from CentOS 6 to CentOS 8. I have several relatively complicated Processwire websites. I am currently downloading all the files via FTP. I will export databases next. I guess I'll use Export Site Profile. Or had that been replaced by something else? New modules that I missed? Or will the FTP'ed files + exported database be enough? Just copy them 1-on-1 to the new server and it will all work? What can go wrong? What are the pitfalls to watch out for?

Thanks wbmnfktr, I had seen that one. That page gives a lot of general, very useful background info on the how and why of permissions, but I was looking for a quick overview/cheatsheet with recommended settings for each processwire directory/file.

Is there an overview/cheatsheet anywhere with recommended permissions for each folder and file? I know permissions are set at installation, but I probably messed things up a bit in a server upgrade or PHP 7.3 has different requirements. I now keep running into permission issues.

Answering my own question: I got directory/files ownership/permission screwed up on /site/assets/cache. Or PHP7.3 handles those differently? /cache and /modules should be writable. I had both on 755, but guess ownership was wrong. Doing this via ssh fixed it: chown -R myserveruser site/assets/cache chown -R myserveruser site/modules chmod -R a+w site/assets/cache chmod -R a+w site/modules Are there other folders/files I should double-check?

I had upgraded my Apache configuration to include PHP7.2 and PHP7.3 for a Laravel-based script on the same server. Somehow it/I messed up a previously fine Processwire site, in a very confusing way. The site still looks fine, but editing template files has no effect whatsoever. It is stuck on some kind of cached version. I have already disabled PHP7's OPcache, cleared browser caches, etc, with no effect. The pages now apparently come from PW's assets/cache/FileCompiler folder, even though I never enabled template caching for this site. I have tried adding "namespace ProcessWire;" to the top of the homepage template file, but then I get this fatal error: My functions.php file pulls data in from another Processwire installation on the same VPS with the following line: $othersitedata = new ProcessWire('/home/myaccount/public_html/myothersite/site/', 'https://myothersite.com/'); That apparently still works fine; the site still displays data from the other installation, but via the "cached" template that I am now unable to change. I don't know where to start with this mess. Does any of this sound familiar to anyone? Any pointers in the right direction would be much appreciated. Edit: Adding "$config->templateCompile = false;" to config.php results in the same fatal error as above.

Is there a way to allow the front-end editing feature for a role, without also giving that role access to the admin area/control panel?

Why doesn't this work? $members = $pages->find("template=user"); foreach($members as $bogus) { // don't use $user if ( $bogus->firstname === $bogus->lastname ) { $bogus->delete(); } } I get this error: If I echo $bogus->fullname, I get a nice list of spam accounts where the first and last name are the same. There has to be a way to let PW allow me to delete them. I have also tried $users->delete( $bogus ) and $users->delete( $bogus, true ) and a few other variations, but keep getting the same error message. Line 1017 is this: if(!$this->isDeleteable($page)) throw new WireException What makes a page not deletable? Any ideas? I have a similar bit that deletes user accounts with numbers in the name fields: $members = $pages->find("template=user"); foreach($members as $bogus) { if ( preg_match('/[><\-0-9]/', $bogus->name ) ) { $users->delete( $bogus ); } } That one works fine. What am I getting wrong with the other one? Edit: I think I figured it out. $firstname === $lastname would also be TRUE for two empty fields, so I guess PW has wisely made that not deleteable somewhere. So you have to check first if either field is set at all. The following seems to work: $members = $pages->find("template=user"); foreach($members as $bogus) { // don't use $user if ( $bogus->firstname && $bogus->firstname === $bogus->lastname ) { $users->delete( $bogus ); } } Or still wrong?

But is it serverless?

To me the beauty of Processwire is that it makes no assumptions how you use it. This module breaks with that logic a bit, probably unnecessarily. I have started editing the css. That is no big deal. I'll look into how to use this field as input for the map marker modules, make them work together. btw, I hope your health problems are under control. Either way, take care.

I need some kind of address field type to store street addresses for events - the map marker modules produce unusable garbage addresses... This module looks solid and probably does what I need for my case. Why does the module assume it will be used for postal mailings? Is that really necessary? Couldn't the UX be a bit more usage agnostic and use the regular admin fonts etc.?

The 'address' field is supposed to output the address you entered. echo $page->map->address; // outputs the address you entered But it actually outputs whatever the map thinks is at that lat-long, with a lot of unnecessary details added, something like this: The address search also insists Water Street is in lower Manhattan when I mean Water Street in Brooklyn. Brooklyn becomes Kings County in map->address; nobody calls it that! You can force the map to select the right location by dragging the pointer. Now the address is: Which is hilarious and completely useless. Is there a way to keep/store the actual "address you entered"? Or else a way to format that map->address into something usable?

This module is great, essential. Unfortunately I can't yet get it to work on my front end. The map doesn't show up due to a javascript/jquery conflict. The module outputs regular jquery script starting with $(function() { ... If I manually add the following alternative to the footer it works fine, the map shows up in all its CartoDB glory: How can I get the module to do the same? Or get around this problem some other way? Edit: I have replaced the following line in MarkupLeafletMap.module: $inlineScript = "<script type='text/javascript'>\n$(function() {\n" . with this: $inlineScript = "<script type='text/javascript'>\nvar jMap = jQuery.noConflict();\njMap(function() {\n" . Now the module works as expected. Could you make that part of the module for next updates? With jLeaflet instead of the more generic jMap. Or is there a good reason not to do it like this or a more cleverer way to avoid jquery conflicts?

Thank you so much adrian. I had been using your Admin Actions module for other things. Super useful. I should have thought of trying that sooner. I have first applied 'Copy Content to Other Field', then used 'Delete Unused Fields'. Both no problems. More clean-up work to do before I can declare victory. I would be pleasantly surprised if the data really is still there, but at least the old fieldtype is gone. Will report back...