I needed the Texy! module for Drupal 6.x branch very early, as my only production site is fully written with Texy and so testing the Drupal 6.x-beta on my side is only possible with Texy available. So I went forward, and ported the module myself.
Attached is a tar.gz archive: Please rename the file, to remove '.txt' extension, which is only needed to attach the file here. The archive contains only changed files (all three .module and .info files), the rest should work as is in Drupal 5.x branch, so please take the other files from the latest 5.x.
This whole thing needs some testing, though. It's just a quick edit, along Drupal's "update modules" guide, which seems to work fine and produce correct output on my tested site (PHP 4, Drupal 6.x-dev updated from 5.1), but I'm far from having tested all the features.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | texy-6-install.patch | 1.94 KB | JirkaRybka |
| texy-6-x.tar_.gz_.txt | 5.88 KB | JirkaRybka |
Comments
Comment #1
dingbats commentedComment #2
havran commentedI promise, i install Drupal 6 and i give some time for this :).
Comment #3
havran commentedOk. Here is (in CVS http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/texy/?pathr..., in releases about 12 hours) it first version which working (for me) on Drupal 6. Syntax highlighting module is still untouched.
Texy Image (with enabled Images as definition list terms) maybe won't work on PHP4 - this still need testing.
Comment #4
havran commentedToday i add syntaxhighlighting support (and i make FSHL as part of distribution). Now if you enable syntaxhighlighting support its (maybe) work immediately. ;) Please test this feature.
Here is release http://drupal.org/node/206705
Comment #5
JirkaRybka commentedGoing to test as time permits. No chance for today, unluckily.
Comment #6
JirkaRybka commentedSorry for delay, time is very limiting... Now I'm testing 6.0 upgrade again, so I tested the new 6.x Texy! too.
Tested only briefly now, seems to work well. But I noticed a few small things:
- INSTALL.txt is out of date (Texy! library now included). Attaching a patch, feel free to change the text...
- README.txt - the same... (Unfortunately I noticed it later, and now no time to roll a new patch, so not included yet.)
- iconv requirement issue: The auto-detection of PHP version works fine, but in my case it ended at WSOD:
Fatal error: Call to undefined function iconv() in /home/jirux/test-webspace/nat6/sites/all/modules/texy/texy/texy.compact.5.php on line 428This is because the Texy! for PHP5 requires not only plain PHP5, it also requires iconv extension, which PHP4 version doesn't require. This extra requirement is not mentioned in the package - now that the library is included, the requirements should be listed in README.txt.
Previously, I was in fact running the PHP4 version, as I installed the files half a year back, on PHP4 (the server was upgraded later). Now, with auto-detection in effect, I get the PHP5+iconv version without question - so Texy! stops working on the server where it worked fine previously.
In the patch, I'm adding an iconv check, which solved the issue for me: Without this requirement satisfied, a fall-back to PHP4 version occurs, and all works fine. With iconv installed, PHP5 version runs. I tested both (pre-/post- iconv installation)
- A little unfinished version number on administrative UI? It says
Module version: here texy_module_version. I didn't investigate on this one, just reporting.Comment #7
havran commentedI've tested patch that you provide, it's work ok. Very soon i try release first beta version. Thank you for testing.
Module version: here texy_module_version- i don't know how to get my module version :DComment #8
havran commentedNow are all changes incorporated into 6.x-1.x-dev version. There is now better requirement check with warnings messages, little changes in default heding size (2 => 3), better explanation about syntax highlighting. I maybe made backport into Drupal 5. :)
Comment #9
havran commentedThere is now Texy! filter module 6.x-1.0-beta1 then i mark this issue as fixed :).
Comment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.