99
break;
case 4:
$title="Критичный";
$pr="image/ballred.png";
break;
}
if ($res_id[6]!=0)
{
$file="<a href='download/$res_id[6]' >
<img src='image/paperclip.png' TITLE='Скачать файл' WIDTH='30'
HEIGHT='30' border='0'>
</a>";
}
else
{
$file="<img src='image/paperclip1.png' TITLE='Нет файла' WIDTH='30'
HEIGHT='30' border='0'>";
}
echo " <center> <table align='center' width='800'> <tr>
<td width='30' class='but1'> <b> $a </b> </td>
<td width='50' class='tz'> $res_id[0] </td>
<td width='50' class='tz'> <img src='$logo' title='$status' WIDTH='30'
HEIGHT='30' border='0'> </td>
<td width='50' class='tz'> <img src='$pr' title='$title' WIDTH='30'
HEIGHT='30' border='0'> </td>
<td width='50' class='tz'> $file </td>
<td width='80' class='tz'> $dat </td>
<td width='200' class='tz'> $res_id[1] </td>
<td width='30' class='tz'> <div>
<a href='index.htm' onclick='return hs.htmlExpand(this)'>
<img src='image/info.png' TITLE='Подробная информация о заявке'
WIDTH='30' HEIGHT='30' border='0'>
100
</a>
<div class='highslide-maincontent'>
<h4>Подробные сведения Заявка № $res_id[0]</h4>
<table width='350' border='1' cellspacing='2' cellpadding='2'>
<tr>
<td width='80' class='table'> Описание</td>
<td width='270' class='kvit'>$res_id[3]</td>
</tr>
<tr>
<td class='table'> Кабинет</td>
<td class='kvit'>$res_id[4]</td>
</tr>
<tr>
<td class='table'> Категории</td>
<td class='kvit'>$res_id[5]</td>
</tr>
<tr>
<td class='table'> Комментарий</td>
<td class='kvit'>$res_id[7]</td>
</tr>
</table>
</div>
</div>
</td>
<td width='30' class='tz'> $isp
</td>
<td width='30' class='tz'> <div>
<a href='index.htm' onclick='return hs.htmlExpand(this)'>
<img src='image/application-x-trash.png' TITLE='Жизненный цикл заявки'
WIDTH='30' HEIGHT='30' border='0'>
</a>
<div class='highslide-maincontent'>
103
$title="Администратор";
break;
case 2:
$title="Пользователь";
break;
case 3:
$title="Диспетчер";
break;
case 4:
$title="Исполнитель";
break;
}
echo " <center> <table> <tr>
<td width='30' class='but1'> <b> $a </b> </td>
<td width='150' class='tz'> $res_id[6] </td>
<td width='200' class='tz'> $res_id[1] </td>
<td width='100' class='tz'> $title </td>
<td width='100' class='tz'> $res_id[4] </td>
<td width='100' class='tz'> $res_id[5] </td>
<td width='45' class=''><form method='post' name='kab' action='udal.php'>
<INPUT TYPE='hidden' NAME='kab' VALUE='$res_id[0]'>
<input type='image' src='../image/cut.png' TITLE='Редактировать данные
пользователя' WIDTH='30' HEIGHT='30' >
</form>
</td>
<td width='45' class=''><form method='post' name='kab' action='udal.php'>
<INPUT TYPE='hidden' NAME='kab' VALUE='$res_id[0]'>
<input type='image' src='../image/delete.png' TITLE='Удалить пользователя'
WIDTH='30' HEIGHT='30' >
</form>
</td>
</tr> </table>\n";
109
}
$query3="insert into status (`nomzav`, openz, flag, iduopen)
values ('$numzav'+1,'$today', '1','$user')";
if(mysql_query($query1) and mysql_query($query3))
{
Header ("Location: newzav.php");
}
else
{
echo "<p class='log'></p>Не получилось</p>";
}
}
With the impending release of WordPress 5.0, the new Gutenberg editor will make its way onto millions of websites. It’s a big change in how content is created, stored and managed. Not to mention the potential compatibility issues that could crop up with some themes and plugins.
As the new editor prepares for full release, we should note that the “Classic” Editor will remain available as a plugin. Activating it will enable site owners to use it in conjunction with Gutenberg or bypass it completely.
Because the Classic Editor affords us a second path, it’s worth considering whether or not to take it. Gutenberg represents a big shift in how WordPress operates. The question becomes, is it really worth utilizing the new editor on an existing site, or is it better to stick with the tried-and-true Classic version?
To answer that question, there are several factors to consider. So, before you take the plunge and switch to Gutenberg, here are a few items you’ll want to think about.
The Past and Future of Your Content
The content on your existing website, along with the way you manage it, has already been established. Odds are that your pages and blog posts follow a specific format that was created long before Gutenberg came onto the scene.
With that in mind, consider whether or not you want to change things to reflect the new capabilities Gutenberg brings. For instance, you might have interest in refactoring your existing content to utilize features like full-width images or multi-column layouts.
However, sites that are heavy in content may require a lot of work to bring up to speed. It might consist of going through every piece of content and laying it out in the new block-based format. Gutenberg can automatically convert legacy posts to blocks, though you’re ultimately the one who will need integrate any customizations.