Information publishing method, device, equipment and storage medium

By calling the applet plug-in in the rich text editor to obtain link information and generate the super text markup language tag, the problem of the applet URL in the HTML page is solved, and the user can jump to the applet page normally.

CN111859204BActive Publication Date: 2025-05-23MICRO INSURANCE AGENCY LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202010623175.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-06-30
Publication Date
2025-05-23
Estimated Expiration
2040-06-30

AI Technical Summary

Technical Problem

When directly inserting the URL, pictures, videos and other information of the applet into an ordinary HTML page, the URL of the applet is invalid, and the user cannot jump to the corresponding page after clicking.

Method used

After monitoring the preset operation trigger for the applet plug-in in the rich text editor, call the applet plug-in to obtain link information, generate the corresponding super text markup language tag, and render it to generate user interface elements, and finally publish these elements in the HTML page.

Benefits of technology

It realizes the validity of the applet URL published in ordinary HTML pages, and users can jump to the corresponding page normally after clicking.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN111859204B_ABST
    Figure CN111859204B_ABST
Patent Text Reader

Abstract

The embodiments of the present application provide an information publishing method, apparatus, device and storage medium, the method comprising: in a rich text editor, if a first preset operation trigger for a small program plug-in is detected, calling the small program plug-in to obtain link information; using the small program plug-in to generate a hypertext markup language tag corresponding to the link information, wherein the hypertext markup language tag carries the link information; rendering the hypertext markup language tag to generate a user interface element; publishing the user interface element on the current hypertext markup language page. In this way, through the small program plug-in provided by the embodiments of the present application, the user can insert the uniform resource locator system of the small program in the rich text editor, and the uniform resource locator system of the small program published on the ordinary hypertext markup language page is valid. After clicking the uniform resource locator system of the small program, the user can jump to the corresponding page.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to an information publishing method, device, equipment and storage medium. Background Art

[0002] RTE (Rich Text Editor) is a WYSIWYG text editor that can be embedded in a browser. It allows users to edit articles or information conveniently so that they can publish articles or information on ordinary HTML (Hyper Text Markup Language) pages as quickly as possible.

[0003] In the related art, a user can insert information such as URL (Uniform Resource Locator), pictures, and videos into a rich text editor to publish the above information in a common HTML page as quickly as possible.

[0004] Since the operating mechanism of the mini program is inconsistent with the HTML standard, if the URL, pictures, videos and other information of the mini program are directly inserted into a rich text editor and used to publish the above information as soon as possible on an ordinary HTML page, the URL of the mini program published on the ordinary HTML page will be invalid. Specifically, after the user clicks the URL of the mini program, they cannot jump to the corresponding page. Summary of the invention

[0005] The purpose of the embodiments of the present application is to provide an information publishing method, apparatus, device and storage medium to achieve the beneficial effect that the URL of the mini-program published on a common HTML page is valid, and the user can jump to the corresponding page after clicking the URL of the mini-program. The specific technical solution is as follows:

[0006] The present application provides an information publishing method, the method comprising:

[0007] In the rich text editor, if a first preset operation trigger for the mini-program plug-in is detected, the mini-program plug-in is called to obtain link information, wherein the link information includes at least one of the following information: a uniform resource locator system of the mini-program and a uniform resource locator system of the hypertext page;

[0008] Using the applet plug-in to generate a hypertext markup language tag corresponding to the link information, wherein the hypertext markup language tag carries the link information;

[0009] Rendering the hypertext markup language tag to generate a user interface element;

[0010] The user interface element is published on the current hypertext markup language page.

[0011] The present application provides an information publishing method, which is applied to a client, and the method includes:

[0012] Displaying a user interface element in a client display interface, wherein the user interface element is generated in a rich text editor by calling a mini-program plug-in according to link information; the link information includes at least one of the following information: a uniform resource locator system of the mini-program and a uniform resource locator system of a hypertext page;

[0013] If a first preset operation trigger for the user interface element is detected, then according to the link information corresponding to the user interface element, the interface displayed on the client is jumped to the interface corresponding to the link information.

[0014] The present application provides an information publishing device, the device comprising:

[0015] A plug-in calling module, configured to, in a rich text editor, call the mini-program plug-in to obtain link information if a first preset operation trigger for the mini-program plug-in is detected, wherein the link information includes at least one of the following information: a uniform resource locator system of the mini-program and a uniform resource locator system of a hypertext page;

[0016] a tag generation module, used to generate a hypertext markup language tag corresponding to the link information using the applet plug-in, wherein the hypertext markup language tag carries the link information;

[0017] A tag rendering module, used for rendering the hypertext markup language tag to generate a user interface element;

[0018] The element publishing module is used to publish the user interface element on the current hypertext markup language page.

[0019] The present application provides a device, including a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus;

[0020] Memory, used to store computer programs;

[0021] The processor is used to implement the above-mentioned information publishing method when executing the program stored in the memory.

[0022] The present application provides a storage medium, wherein instructions are stored in the storage medium, and when the storage medium is run on a computer, the computer is enabled to execute the above-mentioned information publishing method.

[0023] The present application provides a computer program product or a computer program, which includes computer instructions stored on a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the information publishing method provided above.

[0024] The technical solution provided by the embodiment of the present application is that in a rich text editor, if the first preset operation trigger for a mini-program plug-in is monitored, the mini-program plug-in is called to obtain link information, wherein the link information includes at least one of the following information: the uniform resource locator system of the mini-program and the uniform resource locator system of the hypertext page, and the mini-program plug-in is used to generate a hypertext markup language tag corresponding to the link information, wherein the hypertext markup language tag carries the link information, and the hypertext markup language tag is rendered to generate a user interface element, and the user interface element is published on the current hypertext markup language page. In this way, through the mini-program plug-in provided by the embodiment of the present application, the user can insert the uniform resource locator system of the mini-program in the rich text editor, and the uniform resource locator system of the mini-program published on the ordinary hypertext markup language page is valid. After clicking the uniform resource locator system of the mini-program, the user can jump to the corresponding page. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0026] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0027] Figure 1 A schematic diagram of an implementation process of an information publishing method shown in an embodiment of the present application;

[0028] Figure 2 A schematic diagram of a mini-program plug-in interface shown in an embodiment of the present application;

[0029] Figure 3 A schematic diagram of a user interface element shown in an embodiment of the present application;

[0030] Figure 4 It is a schematic diagram of the implementation process of another information publishing method shown in the embodiment of the present application;

[0031] Figure 5 It is a schematic diagram of the implementation process of another information publishing method shown in the embodiment of the present application;

[0032] Figure 6 A schematic diagram of the structure of an information publishing device shown in an embodiment of the present application;

[0033] Figure 7 It is a schematic diagram of the structure of a device shown in an embodiment of the present application. DETAILED DESCRIPTION

[0034] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0035] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0036] In an embodiment of the present application, the provided information publishing method can be specifically applied to an electronic device, which can be a terminal, a server, etc. The information publishing method can be specifically executed by a processor in the electronic device.

[0037] like Figure 1 FIG. 1 is a schematic diagram of an implementation flow of an information publishing method provided in an embodiment of the present application. The method may specifically include the following steps:

[0038] S101, in a rich text editor, if a first preset operation trigger for a mini-program plug-in is detected, the mini-program plug-in is called to obtain link information.

[0039] In an embodiment of the present application, a mini-program plug-in is provided based on the plug-in development capability provided by the rich text editor. For operators, there is no need to worry about environmental issues. The mini-program plug-in can be used to successfully deliver the mini-program's Uniform Resource Locator System (URL for short) and other related information.

[0040] In the rich text editor, if the first preset operation trigger for the small program plug-in is detected, the embodiment of the present application can call the small program plug-in to obtain link information. Among them, for the rich text editor, it is generally embedded in the browser to facilitate the publication of relevant information in the Hypertext Markup Language (HTML) page.

[0041] Specifically, in a rich text editor, if a first preset operation trigger for a button corresponding to a mini-program plug-in is detected, the embodiment of the present application can call the mini-program plug-in to obtain link information.

[0042] For the rich text editor, for example, it can be TinyMCE, Ckeditor, UEditor, wangEditor, etc., which is not limited in the embodiments of the present application.

[0043] The first preset operation may be, for example, a click operation, a slide operation, a selection operation, etc., which is not limited in the embodiment of the present application.

[0044] For example, taking TinyMCE as an example, in TinyMCE, when a user clicks a button corresponding to a mini-program plug-in and triggers the click, the embodiment of the present application can call the mini-program plug-in to receive the link information input by the user, wherein the mini-program plug-in interface diagram is as follows: Figure 2 shown.

[0045] The link information includes at least one of the following information: the URL of the mini program and the URL of the hypertext page. In addition, the user can enter link text, link image and other information in the mini program plug-in. The embodiment of the present application can use the mini program plug-in to receive the link text, link image and the like entered by the user, and the embodiment of the present application is not limited to this.

[0046] For example, the embodiment of the present application utilizes the mini-program plug-in to receive the URL of the mini-program input by the user, as shown below:

[0047] %2Fpages%2Fproduct%2Fdiscovery%2FriskAssessment%2FriskAsk%2Finde;

[0048] Use the applet plug-in to receive the URL of the hypertext page entered by the user, as shown below:

[0049] https: / / www.wesure.cn"data-type=.

[0050] It should be noted that the hypertext page may be an HTML5 page, referred to as an H5 page, which is not limited in the embodiments of the present application.

[0051] S102: Generate a hypertext markup language tag corresponding to the link information using the applet plug-in, wherein the hypertext markup language tag carries the link information.

[0052] S103: Render the hypertext markup language tag to generate a user interface element.

[0053] S104: publishing the user interface element on the current hypertext markup language page.

[0054] For the link information received by the applet plug-in, the embodiment of the present application can publish the link information in the current HTML page. Specifically, the link information can be published in the current HTML page when a publishing instruction input by the user is received.

[0055] In this embodiment of the present application, the link information can be published in the current HTML page in the following manner:

[0056] The mini-program plug-in is used to generate an HTML tag corresponding to the link information, wherein the HTML tag carries the link information; the HTML tag is rendered to generate a user interface element (i.e., a UI element); and the UI element is published on the current HTML page. In this way, the link information is published by publishing the UI element on the current HTML page.

[0057] For example, for the URL of the mini-program and the URL of the HTML5 page received by the mini-program plug-in, the mini-program plug-in is used to generate HTML tags corresponding to the URL of the mini-program and the URL of the HTML5 page, as shown below, wherein the HTML tags carry the URL of the mini-program and the URL of the HTML5 page:

[0058]

[0059] data-url-mp="%2Fpages%2Fproduct%2Fdiscovery%2FriskAssessment%2FriskAsk%2Finde"

[0060] ​data-url-h5="https: / / www.wesure.cn" data-type="mplink">

[0061] Click me to jump

[0062] .

[0063] Among them, the URL of the mini program: data-url-mp, the URL of the HTML5 page: data-url-h5, mplink is used to identify the tag as "URL of the mini program".

[0064] For the HTML tag generated above, the embodiment of the present application can generate a user interface element, i.e., a UI element, by rendering the HTML tag, for example: Figure 3 As shown, the user interface element is published in the current HTML page, and the link information is published by publishing the user interface element in the current HTML page. For the user, the effect seen is no different from the ordinary URL insertion effect.

[0065] The HTML tag is rendered to generate the corresponding user interface element. The specific rendering process is as follows: a rendering tree is generated according to the HTML tag and a preset style, and the rendering tree is drawn by a rendering engine to generate the user interface element corresponding to the HTML tag.

[0066] In addition, the user interface element may be a picture link or a text link, which is not limited in the present embodiment. In this way, the link information may be released in the form of a user interface element.

[0067] It should be noted that, for the HTML tag corresponding to the link information, when the link information includes the URL of the mini program, an HTML tag corresponding to the URL of the mini program is generated; when the link information includes the URL of the hypertext page, an HTML tag corresponding to the URL of the hypertext page is generated; when the link information includes the URL of the mini program and the URL of the hypertext page, an HTML tag corresponding to the URL of the mini program and the URL of the hypertext page is generated, which means that an HTML tag corresponding to the link information can be generated in the embodiment of the present application.

[0068] Through the above description of the technical solution provided by the embodiment of the present application, in the rich text editor, if the first preset operation trigger for the applet plug-in is monitored, the applet plug-in is called to obtain link information, wherein the link information includes at least one of the following information: the uniform resource locator system of the applet and the uniform resource locator system of the hypertext page, and the applet plug-in is used to generate a hypertext markup language tag corresponding to the link information, wherein the hypertext markup language tag carries the link information, and the hypertext markup language tag is rendered to generate a user interface element, and the user interface element is published on the current hypertext markup language page. In this way, through the applet plug-in provided by the embodiment of the present application, the user can insert the uniform resource locator system of the applet in the rich text editor, and the uniform resource locator system of the applet published on the ordinary hypertext markup language page is valid. After clicking the uniform resource locator system of the applet, the user can jump to the corresponding page.

[0069] like Figure 4 FIG. 1 is a schematic diagram of an implementation flow of another information publishing method provided in an embodiment of the present application. The method may specifically include the following steps:

[0070] S401, in a rich text editor, if a first preset operation trigger for a mini-program plug-in is detected, the mini-program plug-in is called to obtain link information.

[0071] S402: Generate a hypertext markup language tag corresponding to the link information using the applet plug-in, wherein the hypertext markup language tag carries the link information.

[0072] S403: Render the hypertext markup language tag to generate a user interface element.

[0073] S404: Publish the user interface element on the current hypertext markup language page.

[0074] S405, after publishing the user interface element on the current HTML page, if a second preset operation trigger for the user interface element is detected, extracting link information in the HTML tag corresponding to the user interface element using a preset script.

[0075] In the embodiment of the present application, the mini program plug-in is used to generate an HTML tag corresponding to the above link information, and the HTML tag is rendered to generate a user interface element, which is published on the current HTML page. In this way, the user interface element exists in the current HTML page, and the link information is published in the form of a user interface element, which is convenient for users to forward, share, and read later.

[0076] For the above-mentioned user interface elements, in an embodiment of the present application, after the user interface elements are published on the current HTML page, when the triggering of the second preset operation for the user interface element is detected, the preset script can be used to extract the link information in the HTML tag corresponding to the user interface element.

[0077] The second preset operation may be, for example, a click operation, a slide operation, a selection operation, etc., which is not limited in the embodiment of the present application.

[0078] For example, Figure 3 The user interface element shown in the figure, after the user interface element is published on the current HTML page, when a click operation on the user interface element is detected, the URL of the mini-program and the URL of the HTML5 page in the HTML tag corresponding to the user interface element can be extracted using a JavaScript script.

[0079] Among them, the HTML tag also includes a target identifier corresponding to the link information. The embodiment of the present application can use a preset script to capture the target identifier in the HTML tag corresponding to the user interface element, and then extract the link information in the HTML tag corresponding to the user interface element based on the target identifier.

[0080] For example, for the HTML tag corresponding to the user interface element, the tag also includes a target identifier corresponding to the link information, as shown below:

[0081]

[0082] data-url-mp="%2Fpages%2Fproduct%2Fdiscovery%2FriskAssessment%2FriskAsk%2Finde"

[0083] data-url-h5="https: / / www.wesure.cn" data-type="mplink">

[0084] Click me to jump

[0085] .

[0086] ​Among them, the URL of the mini program: data-url-mp, the URL of the HTML5 page: data-url-h5, there is mplink, which is used to identify the tag as "URL of the mini program". The embodiment of the present application can use JavaScript script to capture the target identifier mplink in the HTML tag corresponding to the user interface element, and then can extract the URL of the mini program in the HTML tag corresponding to the user interface element according to the target identifier mplink: data-url-mp, the URL of the HTML5 page: data-url-h5.

[0087] S406: Execute a corresponding jump operation according to the link information.

[0088] For the link information extracted through the above steps, that is, at least one of the URL of the mini-program and the URL of the hypertext page, a corresponding jump operation can be performed according to the link information to jump to the page corresponding to the link information.

[0089] Specifically, Figure 5 As shown, the embodiment of the present application can determine whether the above-mentioned user interface element is located in the mini-program; if the above-mentioned user interface element is located in the mini-program, the current HTML page jumps to the mini-program page corresponding to the link information; if the above-mentioned user interface element is not located in the mini-program, the current HTML page jumps to the HTML5 page corresponding to the link information. In this way, different jump operations can be performed based on the different environments where the user interface element is located.

[0090] For example, for Figure 3 The user interface element shown in the figure determines whether the user interface element is located in the mini program; if the user interface element is located in the mini program, the current HTML page jumps to the mini program page corresponding to the link information; if the user interface element is not located in the mini program, the current HTML page jumps to the HTML5 page corresponding to the link information. In this way, different jump operations can be performed based on the different environments where the user interface element is located.

[0091] Among them, for the mini program, there is its unique application identifier, and the same is true for the browser. Therefore, the embodiment of the present application can obtain the application identifier of the application corresponding to the HTML page where the user interface element is currently located, and determine whether the user interface element is currently located in the mini program based on the application identifier.

[0092] For example, assuming that the mini program has its own unique application identifier A, and for the browser, it has its own unique application identifier B, it can obtain the application identifier A of the application corresponding to the HTML page where the user interface element is currently located, and based on the application identifier A, it can be determined that the user interface element is currently located in the mini program, thereby jumping from the current HTML page to the mini program page corresponding to the link information.

[0093] For another example, the application identifier B of the application corresponding to the HTML page where the user interface element is currently located can be obtained, and based on the application identifier B, it can be determined that the user interface element is not currently located in the mini-program, thereby jumping from the current HTML page to the HTML5 page corresponding to the link information.

[0094] In addition, due to the different environments in which the user interface elements are located, there are differences in the jump operations during the execution of the jump operation:

[0095] If the above-mentioned user interface element is located in a small program, a jump component corresponding to the small program can be obtained, and the jump component can be used to jump from the current HTML page to the small program page corresponding to the link information.

[0096] For example, if the above-mentioned user interface element is located in a WeChat mini program, you can obtain the SDK jump component corresponding to the WeChat mini program, and use the SDK jump component to jump from the current HTML page to the mini program page corresponding to the link information. Specifically, use the wx.miniProgram.navigateTo capability in the SDK component to jump from the current HTML page to the mini program page corresponding to the link information.

[0097] If the above-mentioned user interface element is located in the Baidu mini program, the SDK jump component corresponding to the Baidu mini program can be obtained, and the SDK jump component can be used to jump from the current HTML page to the mini program page corresponding to the link information.

[0098] If the above user interface element is not currently located in the mini program, a preset page jump instruction can be used to jump from the current HTML page to the HTML5 page corresponding to the link information.

[0099] For example, if the above user interface element is not located in the applet, window.location.url can be used to jump from the current HTML page to the HTML5 page corresponding to the link information.

[0100] Through the above description of the technical solution provided by the embodiment of the present application, in a rich text editor, if a first preset operation trigger for a mini-program plug-in is detected, the mini-program plug-in is called, and the mini-program plug-in is used to receive link information input by a user, wherein the link information includes at least one of the following information: the uniform resource locator system of the mini-program and the uniform resource locator system of the hypertext page, the mini-program plug-in is used to generate a hypertext markup language tag corresponding to the link information, the hypertext markup language tag is rendered to generate a user interface element, the user interface element is used to publish the link information in the current hypertext markup language page, and after the user interface element is published in the current hypertext markup language page, if a second preset operation trigger for the user interface element is detected, the preset script is used to extract the link information in the hypertext markup language tag corresponding to the user interface element, and a corresponding jump operation is performed according to the link information. In this way, through the mini-program plug-in provided in the embodiment of the present application, users do not need to worry about the environment and can directly insert the uniform resource locator system of the mini-program in the rich text editor, and the uniform resource locator system of the mini-program published on the ordinary hypertext markup language page is valid. After clicking the uniform resource locator system of the mini-program, the user can jump to the corresponding page.

[0101] The present application embodiment provides another information publishing method, which is applied to a client. The method may specifically include:

[0102] Displaying user interface elements in a client display interface, wherein the user interface elements are generated in a rich text editor by calling a mini-program plug-in based on link information; the link information includes at least one of the following information: a uniform resource locator system of the mini-program and a uniform resource locator system of a hypertext page.

[0103] In an embodiment of the present invention, a user interface element (i.e., UI element) can be displayed in the client display interface, wherein the user interface element is generated in a rich text editor by calling a mini-program plug-in based on link information, and the link information includes at least one of the following information: the uniform resource locator system of the mini-program and the uniform resource locator system of the hypertext page.

[0104] If a first preset operation trigger for the user interface element is detected, then according to the link information corresponding to the user interface element, the interface displayed on the client is jumped to the interface corresponding to the link information.

[0105] In the embodiment of the present invention, for a user interface element, if a first preset operation trigger for the user interface element is detected, the interface displayed on the client can be jumped to the interface corresponding to the link information according to the link information corresponding to the user interface element. The specific execution process can refer to the above embodiment, and the embodiment of the present invention will not be repeated here one by one.

[0106] The user interface element can be generated in the following manner: if the second preset operation trigger for the mini-program plug-in is detected, the mini-program plug-in is called to obtain link information; the mini-program plug-in is used to generate a hypertext markup language tag corresponding to the link information, wherein the hypertext markup language tag carries the link information; and the hypertext markup language tag is rendered to generate a user interface element. The specific execution process can refer to the above embodiment, and the embodiments of the present invention will not be described one by one here.

[0107] Corresponding to the above method embodiment, the present application embodiment also provides an information publishing device, such as Figure 6 As shown, the device may include: a plug-in calling module 610, a tag generating module 620, a tag rendering module 630, and an element publishing module 640.

[0108] A plug-in calling module 610 is used to call the mini-program plug-in to obtain link information if a first preset operation trigger for the mini-program plug-in is detected in the rich text editor, wherein the link information includes at least one of the following information: the uniform resource locator system of the mini-program and the uniform resource locator system of the hypertext page;

[0109] The tag generation module 620 is used to generate a hypertext markup language tag corresponding to the link information using the applet plug-in, wherein the hypertext markup language tag carries the link information;

[0110] The tag rendering module 630 is used to render the hypertext markup language tag to generate a user interface element;

[0111] The element publishing module 640 is used to publish the user interface element on the current hypertext markup language page.

[0112] In a specific implementation of the embodiment of the present application, after publishing the user interface element on the current hypertext markup language page, the device further includes:

[0113] The information extraction module 650 is used to extract the link information in the hypertext markup language tag corresponding to the user interface element by using a preset script if a second preset operation triggering the user interface element is detected;

[0114] The page jump module 660 is used to perform a corresponding jump operation according to the link information.

[0115] In a specific implementation of the embodiment of the present application, the hypertext markup language tag also includes a target identifier corresponding to the link information; the information extraction module 650 is specifically used to:

[0116] Using a preset script to capture the target identifier in the hypertext markup language tag corresponding to the user interface element;

[0117] The link information in the hypertext markup language tag corresponding to the user interface element is extracted according to the target identifier.

[0118] In a specific implementation of the embodiment of the present application, the page jump module 660 specifically includes:

[0119] The first jump submodule 661 is used to jump from the current hypertext markup language page to the mini-program page corresponding to the link information when the user interface element is currently located in the mini-program;

[0120] The second jump submodule 662 is used to jump from the current hypertext markup language page to the hypertext page corresponding to the link information when the user interface element is not currently located in the applet.

[0121] In a specific implementation of the embodiment of the present application, the first jump submodule 661 is specifically used for:

[0122] Obtaining an application identifier of an application corresponding to a hypertext markup language page where the user interface element is currently located;

[0123] Determining whether an application identifier of an application corresponding to a hypertext markup language page where the user interface element is currently located matches an application identifier corresponding to the mini-program;

[0124] If the application identifier of the application corresponding to the hypertext markup language page where the user interface element is currently located matches the application identifier corresponding to the mini-program, determining that the user interface element is currently located in the mini-program;

[0125] When the user interface element is currently located in the mini-program, jumping from the current hypertext markup language page to the mini-program page corresponding to the link information;

[0126] The second jump submodule 662 is specifically used for:

[0127] If the application identifier of the application corresponding to the hypertext markup language page where the user interface element is currently located does not match the application identifier corresponding to the mini-program, determining that the user interface element is not currently located in the mini-program;

[0128] When the user interface element is not currently located in the applet, the current hypertext markup language page jumps to the hypertext page corresponding to the link information.

[0129] In a specific implementation of the embodiment of the present application, the first jump submodule 661 is specifically used for:

[0130] When the user interface element is currently located in a mini-program, obtaining a jump component corresponding to the mini-program;

[0131] The jump component is used to jump from the current hypertext markup language page to the small program page corresponding to the link information.

[0132] In a specific implementation of the embodiment of the present application, the second jump submodule 662 is specifically used for:

[0133] When the user interface element is not currently located in the applet, a preset page jump instruction is used to jump from the current hypertext markup language page to the hypertext page corresponding to the link information.

[0134] The present application also provides a device, such as Figure 7 As shown, it includes a processor 71, a communication interface 72, a memory 73 and a communication bus 74, wherein the processor 71, the communication interface 72, and the memory 73 communicate with each other through the communication bus 74.

[0135] A memory 73, for storing computer programs;

[0136] The processor 71 is used to execute the program stored in the memory 73 to implement the following steps:

[0137] In a rich text editor, if a first preset operation trigger for a mini-program plug-in is detected, the mini-program plug-in is called to obtain link information, wherein the link information includes at least one of the following information: the uniform resource locator system of the mini-program and the uniform resource locator system of the hypertext page; the mini-program plug-in is used to generate a hypertext markup language tag corresponding to the link information, wherein the hypertext markup language tag carries the link information; a user interface element is rendered for the hypertext markup language tag; and the user interface element is published on the current hypertext markup language page.

[0138] The communication bus mentioned in the above device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of simplicity, only a thick line is used to represent it in the figure, but it does not mean that there is only one bus or one type of bus.

[0139] The communication interface is used for communication between the above device and other devices.

[0140] The memory may include a Random Access Memory (RAM), and may also include a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located far from the aforementioned processor.

[0141] The above-mentioned processor may be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0142] In another embodiment provided by the present application, a storage medium is also provided. Instructions are stored in the storage medium, and when it runs on a computer, the computer is made to execute the information publishing method described in any one of the above embodiments.

[0143] In another embodiment provided by the present application, a computer program product containing instructions is also provided. When it runs on a computer, the computer is made to execute the information publishing method described in any one of the above embodiments.

[0144] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a storage medium, or transmitted from one storage medium to another storage medium, for example, the computer instructions may be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The storage medium may be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integrations. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive Solid State Disk (SSD)), etc.

[0145] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0146] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0147] The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. A method for publishing information, It is characterized in that The method comprises: In the rich text editor, if a first preset operation trigger for the mini-program plug-in is detected, the mini-program plug-in is called to obtain link information, wherein the link information includes at least one of the following information: a uniform resource locator system of the mini-program and a uniform resource locator system of the hypertext page; Using the applet plug-in to generate a hypertext markup language tag corresponding to the link information, wherein the hypertext markup language tag carries the link information; Rendering the hypertext markup language tag to generate a user interface element; Publishing the user interface element on the current hypertext markup language page; After publishing the user interface element on the current hypertext markup language page, the method further includes: If a second preset operation trigger for the user interface element is detected, the preset script is used to extract the link information in the hypertext markup language tag corresponding to the user interface element; and a corresponding jump operation is performed according to the link information, including: when the user interface element is currently located in a mini-program, jumping from the current hypertext markup language page to the mini-program page corresponding to the link information; when the user interface element is not currently located in a mini-program, jumping from the current hypertext markup language page to the hypertext page corresponding to the link information.

2. The method according to claim 1, It is characterized in that The hypertext markup language tag also includes a target identifier corresponding to the link information; the step of extracting the link information in the hypertext markup language tag corresponding to the user interface element by using a preset script includes: Using a preset script to capture the target identifier in the hypertext markup language tag corresponding to the user interface element; The link information in the hypertext markup language tag corresponding to the user interface element is extracted according to the target identifier.

3. The method according to claim 1, It is characterized in that When the user interface element is currently located in the mini-program, jumping from the current hypertext markup language page to the mini-program page corresponding to the link information includes: Obtaining an application identifier of an application corresponding to a hypertext markup language page where the user interface element is currently located; Determining whether an application identifier of an application corresponding to a hypertext markup language page where the user interface element is currently located matches an application identifier corresponding to the mini-program; If the application identifier of the application corresponding to the hypertext markup language page where the user interface element is currently located matches the application identifier corresponding to the mini-program, determining that the user interface element is currently located in the mini-program; When the user interface element is currently located in the mini-program, jumping from the current hypertext markup language page to the mini-program page corresponding to the link information; When the user interface element is not currently located in the applet, jumping from the current hypertext markup language page to the hypertext page corresponding to the link information includes: If the application identifier of the application corresponding to the hypertext markup language page where the user interface element is currently located does not match the application identifier corresponding to the mini-program, determining that the user interface element is not currently located in the mini-program; When the user interface element is not currently located in the applet, the current hypertext markup language page jumps to the hypertext page corresponding to the link information.

4. The method according to claim 1, It is characterized in that When the user interface element is currently located in the mini-program, jumping from the current hypertext markup language page to the mini-program page corresponding to the link information includes: When the user interface element is currently located in a mini-program, obtaining a jump component corresponding to the mini-program; The jump component is used to jump from the current hypertext markup language page to the small program page corresponding to the link information.

5. The method according to claim 1, It is characterized in that When the user interface element is not currently located in the applet, jumping from the current hypertext markup language page to the hypertext page corresponding to the link information includes: When the user interface element is not currently located in the applet, a preset page jump instruction is used to jump from the current hypertext markup language page to the hypertext page corresponding to the link information.

6. A method for publishing information, It is characterized in that Applied to a client, the method comprises: Displaying a user interface element in a client display interface, wherein the user interface element is generated in a rich text editor by calling a mini-program plug-in according to link information; the link information includes at least one of the following information: a uniform resource locator system of the mini-program and a uniform resource locator system of a hypertext page; If a first preset operation trigger for the user interface element is detected, then according to the link information corresponding to the user interface element, the interface displayed on the client is jumped to the interface corresponding to the link information, including: when the user interface element is currently located in the mini-program, the current hypertext markup language page is jumped to the mini-program page corresponding to the link information; when the user interface element is not currently located in the mini-program, the current hypertext markup language page is jumped to the hypertext page corresponding to the link information; The user interface element is generated in the rich text editor by calling the applet plug-in according to the link information, and specifically includes: If a second preset operation trigger for the mini-program plug-in is detected, calling the mini-program plug-in to obtain link information; Using the applet plug-in to generate a hypertext markup language tag corresponding to the link information, wherein the hypertext markup language tag carries the link information; The hypertext markup language tag is rendered to generate a user interface element.

7. An information publishing device, It is characterized in that The device comprises: A plug-in calling module, configured to, in a rich text editor, call the mini-program plug-in to obtain link information if a first preset operation trigger for the mini-program plug-in is detected, wherein the link information includes at least one of the following information: a uniform resource locator system of the mini-program and a uniform resource locator system of a hypertext page; a tag generation module, used to generate a hypertext markup language tag corresponding to the link information using the applet plug-in, wherein the hypertext markup language tag carries the link information; A tag rendering module, used for rendering the hypertext markup language tag to generate a user interface element; An element publishing module, used for publishing the user interface element on the current hypertext markup language page; After publishing the user interface element on the current hypertext markup language page, the device further comprises: If a second preset operation trigger for the user interface element is detected, the preset script is used to extract the link information in the hypertext markup language tag corresponding to the user interface element; and a corresponding jump operation is performed according to the link information, including: when the user interface element is currently located in a mini-program, jumping from the current hypertext markup language page to the mini-program page corresponding to the link information; when the user interface element is not currently located in a mini-program, jumping from the current hypertext markup language page to the hypertext page corresponding to the link information.

8. An information publishing device, It is characterized in that It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, for implementing the method steps described in any one of claims 1 to 6 when executing a program stored in a memory.

9. A storage medium having a computer program stored thereon, It is characterized in that When the program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

10. A computer program product, comprising computer instructions stored on a computer-readable storage medium, wherein a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method according to any one of claims 1 to 6.

Citation Information

Patent Citations

  • Rich text data processing method and device, electronic equipment and computer storage medium

    CN111274760A