Community Forum

If you have questions about my software, chances are this forum has the answers.

You'll need to register before you can post on the forum to ask your question or to answer another one. A reply will be posted to each and every question that is asked so there is no need to double post or bump your post. I do my best to answer promptly but in some cases it may take a day or two. If you bump your post, it may be removed. Bear with me and I`ll get your question answered quickly.

Here are a few tips to help you to get your questions answered more rapidly.

IMPORTANT: Posts in English only. I don't have a translator and I'll be unable to understand your message properly and will probably delete it.
SEARCH: Use the search option to see if your question has been answered on the forum before now or if there is an answer in the documentation of your software.
PRIORITY SUPPORT: If you have purchased a commercial version of any software, using the contact option at the licence centre ensures a faster response.
AUTO DELETION: Accounts older than 5 days, with no posts or topics, are automatically deleted. Only register if you are thinking of posting.
LINKS: Any links posted are not clickable and must be copied / pasted into your browser address bar.

You are not logged in.

#1 jgbrown54 23-08-2019 04:50:14

[urlnew] works in Google Chrome but not in Edge. Link is opened in current window instead of a new tab.

To correct this, modify the following lines in control\classes\class.bb.php

From:
  // For url tags..
  public function urlParser($text) {
    $text = preg_replace('#\[urlnew\=(.+)\](.+)\[\/urlnew\]#iUs', '<a href="$1" onclick="window.open(this);return false">$2</a>', $text);
    $text = preg_replace('#\[urlnew\](.+)\[/urlnew\]#iUs', '<a href="$1" onclick="window.open(this);return false">$1</a>', $text);
    $text = preg_replace('#\[url\=(.+)\](.+)\[\/url\]#iUs', '<a href="$1">$2</a>', $text);
    $text = preg_replace('#\[url\](.+)\[/url\]#iUs', '<a href="$1">$1</a>', $text);
    return $text;
  }

To:
  // For url tags..
  public function urlParser($text) {
    $text = preg_replace('#\[urlnew\=(.+)\](.+)\[\/urlnew\]#iUs', '<a href="$1" target="_blank" onclick="window.open(this);return false">$2</a>', $text);
    $text = preg_replace('#\[urlnew\](.+)\[/urlnew\]#iUs', '<a href="$1" target="_blank" onclick="window.open(this);return false">$1</a>', $text);
    $text = preg_replace('#\[url\=(.+)\](.+)\[\/url\]#iUs', '<a href="$1">$2</a>', $text);
    $text = preg_replace('#\[url\](.+)\[/url\]#iUs', '<a href="$1">$1</a>', $text);
    return $text;
  }

This adds in the target="_blank" which will open a new tab in Edge. I believe this fix works for all browsers.

Last edited by jgbrown54 (23-08-2019 04:52:06)

#2 msworld 23-08-2019 06:09:11

This adds in the target="_blank" which will open a new tab in Edge. I believe this fix works for all browsers.

It does, but it`s deprecated and is not part of the HTML5 spec. This is the reason I don`t use it. Thankfully, MS are ditching Edge in favour of a Chromium based browser soon, so should be resolved?

#3 jgbrown54 24-08-2019 07:26:54

That makes sense David. But in the mean time it does provide a fix for Edge and does not cause any issues in other browsers as they ignore it. That's why I left in the onclick functionality. Remnants of Edge may be around on some PCs and phones for some time to come. Even though Microsoft has finally had the wisdom to realize that they are not the final word on internet browsers and that the W3C is seeking to standardize. So for the user that wants to strictly adhere to the HTML5 standard even though not all browsers completely adhere to it, they can leave it the way it is. But for the user that wants to provide maximum functionality to their customers, it's here for the taking. smile

Just remember to use at your own risk.

#4 jgbrown54 24-08-2019 07:56:46

By the way...….I am new to your products and if this non-issue is all I can find wrong, then your team has done an excellent job. WebBlog is intuitive and it's method of resizing based on browser/screen resolution works very well. I'm not a big fan of mark-down but it does get the job done. I noticed that there are more mark-done codes than buttons on the editor screens. Is this by design or would it be okay if I provided some code to implement them. I would also like to work on implementing an optional TinyMCE capability. This would greatly expand the formatting of journals and boxes.

#5 msworld 24-08-2019 10:44:48
jgbrown54 wrote:

That makes sense David. But in the mean time it does provide a fix for Edge and does not cause any issues in other browsers as they ignore it. That's why I left in the onclick functionality. Remnants of Edge may be around on some PCs and phones for some time to come. Even though Microsoft has finally had the wisdom to realize that they are not the final word on internet browsers and that the W3C is seeking to standardize. So for the user that wants to strictly adhere to the HTML5 standard even though not all browsers completely adhere to it, they can leave it the way it is. But for the user that wants to provide maximum functionality to their customers, it's here for the taking. smile

Just remember to use at your own risk.

Uderstand and I agree with your comments. smile

#6 msworld 24-08-2019 10:53:06
jgbrown54 wrote:

By the way...….I am new to your products and if this non-issue is all I can find wrong, then your team has done an excellent job. WebBlog is intuitive and it's method of resizing based on browser/screen resolution works very well.

Thank you very much. smile

jgbrown54 wrote:

I'm not a big fan of mark-down but it does get the job done. I noticed that there are more mark-done codes than buttons on the editor screens. Is this by design or would it be okay if I provided some code to implement them. I would also like to work on implementing an optional TinyMCE capability. This would greatly expand the formatting of journals and boxes.

Actually I am planning to add a wysiwyg editor in the next update. I`ll need to have a think about it though as some of the existing tags might break. Maian Weblog doesn't use Markdown, just BB code tags. You can certainly make code changes to suit your own requirements, no problem there.

Board footer

Maian Script World - Free PHP Software for Personal or Business Use.
© 2003-2019 Maian Script World & David Ian Bennett.

2Checkout.com is an authorized reseller of goods and services provided by Maian Script World

Free PHP Software / Responsive PHP Scripts / Lightweight PHP Software / White Label PHP Software