rraub
Forum Replies Created
-
Forum: Plugins
In reply to: [SSH SFTP Updater Support] Need to update included phplibsec dependencyI just replaced the phpseclib folder within this plugin with the 1.0.1 version from github. I was hoping the maintainer of this plugin would have addressed this issue by now. phpseclib is available in composer, so it wouldn’t be too hard for this plugin to switch over to using composer and that would make future upgrades much easier.
the fix to this issue will be coming in v1.7.2
Looks like this issue has been addressed with the new 1.7.0 release.
Forum: Plugins
In reply to: [HTML Editor Syntax Highlighter] Big Screen IssueLooks like this isn’t an issue anymore with the new 1.7.0 release
Sounds like a duplicate issue to https://ww.wp.xz.cn/support/topic/fix-for-top-of-editor-being-cut-off-from-view?replies=6
Forum: Plugins
In reply to: [HTML Editor Syntax Highlighter] Big Screen IssueI think you might have the same issue in this topic: https://ww.wp.xz.cn/support/topic/fix-for-top-of-editor-being-cut-off-from-view?replies=6
+1 this is a major annoyance and a simple fix.
FYI i’ve forked this plugin, made this fix and one other on it:
https://github.com/gios-asu/wp-html-editor-syntax-highlighterFYI I made these changes on our fork of your plugin: https://github.com/gios-asu/wp-html-editor-syntax-highlighter
Forum: Networking WordPress
In reply to: Technical limitations to running on non-standard portI had the same question! it sure makes development difficult for multiple app’s fighting over the same ports.
I traced the port restrictions back to when WordPress and WordPress MultiSite (formally called WordPress MU) were on different code bases.
Searching through the old forums brought up a similar topic:
https://mu.ww.wp.xz.cn/forums/topic/14587From what I can tell the reasons are mainly “it’s complicated” and would require lots of little changes across the codebase.
- Ports intentionally get filtered out of the url routing. (The route should be the same if the page is under ssl or not)
- links and configurations currently always exclude the port (which is desirable when on the standard ports)
Really there is no reason I see why multi site can’t run on a non-standard port, if someone spends some time to work with all the edge cases.
Forum: Plugins
In reply to: [Redirection] wildcard redirectionJust use a full url instead of a relative path for the destination.
source url: /old-page
target url: http://newdomain.com/new-page