You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 16 of 29)
pilch73 wrote:still got the admin alert
Seems like you don't have overwritten all old files. Try to copy and overwrite all files in directories "admin", "include", "lang", "styles" and *.php files in the forum root directory from 1.3.3 installation package. Then remove *.php files in "cache" directory.
Slavok told you that similar functionality is included into the core. Use "Moderate topic" link. Select posts you want to move and press "Split selected posts" button. By doing this you'll create a temporary topic. Then you have to go to "Moderate forum", select the destination topic and the temporary topic and merge them.
You have to define FORUM_ROOT correctly. This code must work fine:
define('FORUM_ROOT', './forum/');
Try to save all language files in UTF-8 encoding (without BOM). Letters like "ö" should be saved and displayed correctly if the file is saved in UTF-8.
Actually, the poster name on the same row as a topic title is a bug fixed in 1.3.3. You can undo the fix.
Find this code in Oxygen.css (line 970):
.brd .main-content .main-item .item-subject .hn,
.brd .main-content .main-item .item-subject p {
margin: 0 0 0 1.5em;
}
Change it to
.brd .main-content .main-item .item-subject .hn{
margin: 0 0 0 1.5em;
display: inline;
}
.brd .main-content .main-item .item-subject p {
margin: 0;
display: inline;
}
However, if you undo the fix you'll probably encounter another bug.
Maybe it's better to connect error_reporting with the FORUM_DEBUG constant. If FORUM_DEBUG is defined, all errors and notices should be displayed.
pm_email works with pun_pm 1.2.5.
You can modify pm_email for pun_pm 1.2.6 (released 2 days ago):
1. Open manifest.xml of pm_email.
2. Find the following string (line 119):
<hook id="pun_pm_sent_pre_redirect"><![CDATA[
3. Change "pun_pm_sent_pre_redirect" to "pun_pm_fn_send_message_pre_redirect".
4. Reinstall pm_email.
I think clearing cache directory will fix the issue.
I think we should keep only language packs for the last release. It's unlikely that somebody wants to download a language pack for 1.3.2 when 1.3.3 is released.
Thanks for your explanation.
I'm afraid we can't change function names right now in the 1.3 branch. There are many extensions released, so we have to support the compatibility.
However, this should be taken into account in future releases.
Works fine for me. What extensions do you have installed?
Maybe table names have a prefix (the prefix is set during installation)? Then you should run a query
UPDATE <prefix>users SET style="<<new style name>>"
Nice :)
By the way, after releasing 1.3.3 we returned to the styles development. If everything goes Ok, we'll finish these styles.
Yes, there is a change in lang/English/index.php, 'Mark all as read' entry is obsolete and has been removed. One of extensions installed still uses this obsolete entry.
Seems like Slavok is right and the bug is in a extension. Try to disable extensions one by one and to find what extension causes the issue.
Ok, I've got it.
You have to change extern.php, line 483:
'link' => forum_link($forum_url['topic_new_posts'], array($cur_topic['id'], sef_friendly($cur_topic['subject']))),
You can replace 'topic_new_posts' by 'topic' (for links to topics) or 'topic_last_post' (for links to last posts). Btw, this could be a little extension.
Seems like there is an error in your language files. Chek the entry
'Mark all as read' => 'Mark all topics as read',
in the lang/English/common.php, line 129.
I don't understand what you want to do.
Please, describe in details: What have you done? What have you obtained? What do you expect?
Smith, I've added a lot of hooks to pun_pm (one of old two hooks is renamed). You may get pun_pm from SVN and use it. Let me now when you finish testing, I'll release a new version.
No changes in templates were made after the release of 1.3.2.
You can find update instructions in the news topic.
You are right.
install.php, line 87:
header('Content-Type: text/xml; charset=utf-8');
Obviously should be text/html.
Maybe the page is not a valid XHTML page. What version did you install, 1.3.2 or 1.3.3? We'll check it.
Hm, install.php doesn't seem to deal with XML. What browser do you use?
Posts found: 376 to 400 of 703