Upgrade dompdf to newer version - dompdf

I have an old version of dompdf, and need to upgrade to support my headers properly. How would I go about doing this? I tried just copying the new files in my directory, but no go...

From/to which versions? dompdf 0.5.x and 0.6.x are drop-in compatible, though you may need to reset your font directory, namely by removing the dompdf_font_family_cache file. The file may or may not have a .php extension depending on which version you're starting from. Do not delete the file that includes .dist in its name.
You will, of course, need to reload any fonts.
0.7.0 requires a bit more work on the implementation side. Easiest path is to completely replace the dompdf directory. Usage is mostly the same, though some method names have changed and you'll need to reference the dompdf namespace.
There's a work-in-progress migration guide that may help and the usage documentation might also be useful.

Related

What is the directory structure for adding Sorbet RBIs to a gem?

I have a gem I want to add types to (either by submitting a PR or by forking to use just in my project), but the documentation does not give any more guidance other than to create an /rbi folder.
Thinking out loud, should it mirror the files in lib/ with added type signatures, or should it be one large file (per version?) like the signatures in sorbet-typed?
I don't know of any gems doing this yet, and the documentation doesn't mention it either.
I recently went through this process for one of my gems - pdf-reader. It was my first experience with sorbet (so I'm no expert), and I also noticed the lack of documentation for the specific use case of adding types to a gem.
I ended up generating the initial rbi file using parlour, which put them all into a single file: https://github.com/yob/pdf-reader/blob/480aa240a531cd6f97a46a29279f19025821e886/rbi/pdf-reader.rbi
Sorbet seems happy with that, so I haven't changed it.

Where can I restore Pandoc's configuration

I have Pandoc 2.2.3.2 installed on my system via Anaconda. The Reveal.js slideshows I convert with it do not work, because the inserted links to the Reveal.js code seem to be wrong. The documentation states that the default URL should be 'https://unpkg.com/reveal.js#^4/'. However, in my generated slides they turn out as in for example <script src="reveal.js/js/reveal.js"></script>, so the base part of the URL seems to be missing.
Fixing the URL by setting the revealjs-url variable is unfortunately not enough, because the files seem to be located under 'dist' rather than the various prefixes 'js', 'css' that I find in my document now.
Where could this be configured in Pandoc? I have searched the documentation and grepped for possible configuration files on my hard drive, with no luck so far.
You should be able to fix this by using an URL pointing to a reveal.js 3.* version. The versioning issue has been fixed in newer versions (pandoc 2.10 and later). Instead of always using the latest reveal.js version, pandoc now pins a specific version.
See this pandoc issue for more details.

How to find version of CKEDITOR Inline

I have CKEDITOR inline embedded in my portal but I am unable to find the version of CKEDITOR.
CKEDITOR.version returns %VERSION%
The changes.md file doesn't exist either.
If CKEDITOR.version is set to %VERSION% it means that you're using a development version of CKEditor, not a release (or that it was built incorrectly). Lack of changelog means that someone removed it... Not a very fortunate move as well. So if you don't know its source and its not a clone of CKEditor repository it will be very hard to guess what version it is. You can try to check CKEDITOR.revision and compare it with http://github.com/ckeditor/ckeditor-dev. But if that fails too, then the only solution will be to compare code manually.

sublime text 2 portable update not sure how?

I have just (finally) started using sublime text 2, and I am liking it so far (apart from lack of intellisense / autocompletion :(, though tried codeintel but its not what I expected), I am moving from netbeans (can't afford to use it because of memory eating nature :(). Anyway My current issue is I don't know how I can use latest update of sublime text 2 (portable on windows), it kept prompting me about update and once I listened to it and it downloaded new version but there was no step involved in actually updating the existing version to new one instead I have another portable version with newer files, and my issue is i have install several plugins in the old version and I don't know how I can use those in this new version :(.
Note: It just started saying me this version has expired so thats why I am seeking help so I can use new version but with my already installed plugins (emmet, js minifier etc etc :().
I have googled alot but found no windows based guide which helps me solve my issue :(.
Thanks in advance.
Assume that your old version is installed in Sublime.old, and the new version in Sublime.new. Make sure Sublime Text 2 is closed, then move the Sublime.new\Data folder to someplace else (like your Desktop, for now), just in case anything breaks. Then, copy (don't move) the Sublime.old\Data folder to Sublime.new. Fire up the program and check to see that everything is there, and works properly. Please note that this method will not work when upgrading from ST2 to ST3, as there are major differences in the way plugins are run.

How to update SQLITE3 version of Xcode?

I already searched on the net a way to update the SQLITE3 version of Xcode, but I didn't found any working way. It is a way to do it?
If you want to use your own version of sqlite3, perhaps because you want to use newer features only provided by a later version, then probably the best thing to do would be to create an Xcode static library project to build sqlite3 and then include that library with your app (statically linked). This will avoid using the system version.
This should be fairly trivial, given the number of source files that make-up sqlite3.
You could probably make a dynamic library version, but that's slightly more complicated, though certainly possible.

Resources