Sorry. I was running tests. It was a test post. I should have used a new topic. I forgot you subscribe to these.

I received an email saying you responded to this question, but the image was blank and the post doesn't appear here. Did you delete it?

I will have to look into it as i was unaware of the issue.

More Tinymce woes. I just discovered this because a member who uses a phone has told me. Tinymce table and photo uploads aren't responsive. I've found dozens of solutions on the web but none seem to work. Is there a simple solution for Cheetah?

As none off the Cheetahwsb members answered this question, I've decided to try a less demanding approach. Unfortunately I'm not sure if Cheetah can handle my request and I wouldn't know how to do most of the setup even if it did. Deano, maybe you can help me here? What I'd like to do is this: 1. A person signs up but only has certain privileges such as updating their profile, uploading photos and viewing other profiles. 2. These limited  privileges would remain in place until

I currently run two sites. I closed the third one down a few weeks ago. You're correct, I do run 1.3.0 and most of the Github updates up until 4 months ago.  I pick the eyes out of the updates, but the forum one does interest me. I now know why the forum is so quiet. One Boonex member moved over a few weeks ago, but I'm not sure he's tried Cheetah yet. It's so difficult to get people interested.

Actually you have several database changes. Keep in mind you installed your site from a version from github which is somewhere in between the last official release and whats currently there. So there are many database changes from the actual last official release.I could do a simple update method as you suggest. Based on my license server hits for license checks, there are only 4 people using cheetah. And includes you and me. So there are actually only 2 others still using it.PHP

I hear you. I've made hundreds of changes to my site., but most are in the template areas. However, I have made a few changes to the core, but none have involved updating the database to my knowledge. Most are just cosmetic enhancements. I tried keeping a record of the core changes, but they got out of hand. Before I replace a core file from Github, I compare it with the file on my site. So far I've been lucky and the changes are minimal. I am concerned about an upgrade, especially t

The only way to do it is to locate the code changes in github and apply them. And yes, a database change is needed too.But this method of doing updates is what is preventing the supplied update script from working which is the reason i have not yet released a update because i know it will not work on your site without producing database errors. There are other possible sites that GeekGirl had patched in a similar way that also may have problems.Thats the reason i am tr

I put this one up as a suggestion several months ago: