Jump to content

Iain

Members
  • Posts

    24
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling

Iain's Achievements

Jr. Member

Jr. Member (3/6)

2

Reputation

  1. We've developed a problem with our 2.1 installation of PW so would like to reinstall the main files to try and sort things out. The problem is it's a 2.1 installation and I can't find the 2.1 version to download. It's not on Github any more by the looks of it. Where can we get this from now? Or will the 2.2 version install seamlessly over the top with the existing data? Thanks Edit: (Sorry, just found the readme notes about upgrading from 2.1... can probably scrap this now...)
  2. Not the whole "wire" folder, just the "core" folder within that. As for the admin theme, I must confess I've just realised I hadn't read the instructions properly. I'd uploaded it into the wire folder, not the site folder. No wonder it broke when I renamed it... It's all straight and in the right place now!
  3. Right. Resetting the theme broke something, so I re-uploaded the original templates-admin folder and that sorted that little issue. But the images problem remained. While I had the download handy I uploaded the entire core directory again, and that seems to have fixed the main 500 error problems. I've also re-enabled the other admin template and that hasn't broken anything, so I guess something was messed up in the core directory. Weirdly I downloaded the "broken" core folder and compared them; the only difference seems to be that Notepad++ recognises the newly installed one as UNIX, and the other non-working version as Windows/Dos. Whether that's a result of FTP activity I don't know, but my host is Linux based so it seems odd to be picked up as a Windows file. Oh well. It's working. Thanks for all of your suggestions
  4. I've just done a full DB repair and that didn't work, I've just done a full check as well and every table came back OK. I'll switch the theme back when I get home... what's the best way of doing that?
  5. Right. New development. I added the "images" field into my nicely working template, and can no longer edit any of the pages. Not only that, whenever I try to remove the field from the template in the backend, I get the same error... so I'm a bit stumped. I'm using the Moderna admin template if that makes any difference... Update: I managed to remove the images field by scrubbing that row in the database table, and created my own field called "Pictures" with the basic unlimited image settings (to replicate the default images field). Assigning that new field to the template has the same effect - that error when I edit the page or try to remove it from the template. It's clearly an issue with the image uploader, but I've got absolutely no idea how to fix that...
  6. It's on a dev server at the mo, so once it goes live I'll leave the dev version set up and give you a shout
  7. Well I've worked out where the problem lies, even if I can't fix it easily. It's the default templates. I went into the database and changed the template id on my old 404 and About pages to that of my new pages and it now works... not sure what it is about the standard templates that's breaking it though.
  8. It's the latest version of Processwire, running on PHP 5.3.13 and Apache 2.2.22...
  9. Hi folks. I've set up a new site, and set up new templates and pages in exactly the same way as I have done before. But whenever I try to edit a default page (like the 404 page, the site map or whatever) in the admin section I get a 500 error. Turning on the debug mode gives the following error: Fatal error: Class 'Pagefiles' not found in /home/ [...] /wire/core/Pageimages.php on line 20 Obviously I've taken some of the path out, but you get the idea. I can edit my own new pages fine, but whenever I try to edit the others this comes up. The Pagefile file is in the right place, and the error is on a line which defines a new class which extends the Pagefiles class. Any ideas what I can try? Thanks
  10. Ah yeah, I did something with that Salt line. Might've copied it. Can't remember. This site should be live tonight all being well, so I'd be interested in testing the upgrade routine on our dev server if you need someone to test it
  11. Right. I installed a new copy of PW, imported the database and got loads of errors I didn't understand. Realised I'd copied PW2.0 data into a PW2.1 installation, so installed PW2.0 afresh and imported the data and the old files (except config.php, .htaccess and the wire folder. It worked mostly, but wouldn't log me in. Said the username and password was wrong. There was much swearing and tantrum throwing, until I followed Sevarf's idea which sorted it. If the deadline for this going live wasn't tomorrow, and if they weren't still throwing stuff at us that we asked for 3 months ago, this might not be so stressful. Thanks for the help though everyone, I don't know if it was the htaccess file that broke it, I've tried too many things to know for sure!
  12. So the site we're working on has been moved to a nearly-live server. After a battle with getting the htaccess file to be recognised it's all working, except the logins. It's recognising the usernames and passwords as being correct (it doesn't bring up an error unless we type something in wrong) but it just redirects to the login page instead of taking us into the list of pages... Any ideas?
  13. Perfect, did just the job, thanks for the help
  14. Thanks Ryan, I've sent you a PM. As for custom modules, we've got nothing plugged in. This is a pretty vanilla version we're running...
  15. Hi Ryan, We're getting stuff in Word, but copying it into Notepad++ (which uses basic UTF-8 encoding and strips out all of Word's crappiness), then copying and pasting into the TinyMCE window. The characters don't show up in the editor at all, not in the HTML editor window nor the WYSIWYG, just when they're rendered onto the website. This comes up in both IE and Firefox which are using UTF-8 as well.. In fact I've just realised that you can type a word straight into the editor, put in 2 spaces before the next word and you get the same thing happening, so it's not a copy/paste problem I assume.
×
×
  • Create New...