WYSIWYG with history and working copy

[VSG]

Hi there!

I know this is annoying, but is this compatible with 2.8.2 - OR what it should have been from the start: is it integrated into WB 2.8.2?

This module is a must-have and a show-stopper if it doesn't work. Right now I don't have the time to test, but would be nice if there was any info on whether it works or will eventually end up as a default-core in WB.

Thanks again for all the time and effort put into this!
Best regards,
VSG

[VSG]

In case anyone is interested, the module does work with WebsiteBaker 2.8.2 (only tested with FCKEditor).

If one wants to implement it, you should proceed as follows:
1. install current version 2.7.5.4 from here
2. apply the "modify.htt"-patch from this post
3. if you want an indicator in the page-tree which page has a working-copy-version you should apply this patch (very useful)
4. another patch can be found here that is useful to get a confirmation before leaving a page in which the changed content hasn't been saved yet (asks every time, even if nothing has changed, so might be annoying)

As I said, this module is essential in my opinion. At least when managing big sites. Mine has more than 1000 pages now and I can't think of running it without this feature.

Dear WB-developers: PLEASE make this a default-feature for WB in future versions. Since the functionality can be switched off/on in the WYSIWYG-section, those users who don't want to use it, won't. And those who realise the benefit of it, will be grateful for it. Thanks!

Best regards,
VSG

[dbs]

Dear WB-developers: PLEASE make this a default-feature for WB in future versions

i subscribe

[sky writer]

Very nice work!

I have a question.  Since this is a core replacement, do you still need to do this final installation step from your documentation:

reload modules (Add-ons -> Advanced: reload modules)

I did it and all of my previous WYSIWYG content is gone.  Not to worry, as this was a test site, but I thought I would mention it, to avoid someone following the documentation and losing their data.

[ruebenwurzel]

Hello,

wich version of WB did you use? I'm pretty shure this will not work with WB 2.8.3.

Matthias

[VSG]

Well, I actually do have it working on a website that I use regularly. However this was updated from a working 2.8.2 installation and I simply copied the module here into the WYSIWYG folder without applying the database update - since that was already in place due to the previous installation.

But reloading the modules did not erase the contents.

In the thread regarding 2.8.3 I wrote that it works. Weeks into using it, I don't have any issues.

Best regards,
VSG

[ruebenwurzel]

Hello,

In the thread regarding 2.8.3 I wrote that it works. Weeks into using it, I don't have any issues.

You wrote that it worked on 2.8.2. But in WB 2.8.3 there are bigger changes in the WYSIWYG-Modul and in the backend_themes. So if you upgraded from 2.8.2 to 2.8.3 the standard way your changes should be overwritten and "WYSIWYG with working history and working copy" shouldn't work. Replacing the "old" patch files wich worked in 2.8.2 I'm pretty shure does not work in WB 2.8.3. To get this Core-Replacement working in WB 2.8.3 you have to incooporate the changes in the new WB 2.8.3 files.

Matthias

[VSG]

Replacing the "old" patch files wich worked in 2.8.2 I'm pretty shure does not work in WB 2.8.3. To get this Core-Replacement working in WB 2.8.3 you have to incooporate the changes in the new WB 2.8.3 files.

No matter if it should work or not, I can assure you that it does. I updated from 2.8.2 which featured the WYSIWYG-mod already, applied the WebsiteBaker update to 2.8.3 and then just copied the files from the mod (not my old installation!) - that's it. I'm using the Argos Backend theme and have updated about 20 pages since the update. Using both the "working copy" feature and publishing the content directly, so that the previous is stored in the history.

And I don't have any issues as of now. I sure hope they won't be coming just because I said so .
Best regards,
VSG

[ruebenwurzel]

Hello,

as long as you do this:

... you have to incooporate the changes in the new WB 2.8.3 files...

means: please don't use the patched files
- admin/pages/index.php
- modules/wysiwyg/modify.php
- .../templates/modify.htt
from WB 2.8.2.

It only works when you incooporate the changed code in these files directly in the WB 2.8.3 files. Otherwise you shure will run into issues.

Matthias

[sky writer]

Hello,

wich version of WB did you use? I'm pretty shure this will not work with WB 2.8.3.

Matthias

2.8.1

[sky writer]

But reloading the modules did not erase the contents.

Maybe I am doing something wrong.

If I just ftp the WYSIWYG with History files, and then run the 'upgrade.php', everything seems to run fine.  So I am curious why I need to Reload the Modules?

And when I do go to Modules / Advanced, I get the added options at the bottom to "Execute module files manually", the three options are "install.php, upgrade.php, uninstall.php", then there is a RED warning
"Warning: Existing module database entries will get lost. Only use this option if you experience problems with modules uploaded via FTP."

If I manually run the install.php, then all my previous WYSIWYG info is erased, just as the warning describes.

EDIT:

I have never had to "reload modules" before, and I just realized that I was not following the directions correctly.  I just reloaded modules, but my question still stands:
Is this step necessary?  Everything seemed to be working before this step.

[sky writer]

How do you modify the default settings for this module?
I would like the default to be 'active' for this module, and to make the max history to be 0.

I want to change the defaults because I will be adding this module to a bunch of sites, and I don't want to have to go through every page on the site and set it up the way I like.

[marmot]

Hi,

How do you modify the default settings for this module?
I would like the default to be 'active' for this module, and to make the max history to be 0.

in upgrade.php edit lines 50 from DEFAULT 6 to DEFAULT 0 and line 52 from DEFAULT 0 to DEFAULT 1, before upgrading.

I want to change the defaults because I will be adding this module to a bunch of sites, and I don't want to have to go through every page on the site and set it up the way I like.

hmm using the historie makes only sense when you edit a wysiwyg section, so there is no need to set the option in advance on every page. While editing the content one additional click is too much? But of course you could forget to click . But that's just my opinion an I hope my hint above can help you out.

regards

[sky writer]

Thanks for your help.

To clarify why I want the defaults set ahead of time, I have dozens of sites, some with hundreds of pages, and clients editing them themselves.  So, no, one additional click is not too much for me.  But it may be for my clients.